Add gitleaks-scan workflow (public-repo secret scanning) - #6
Merged
Merged
Conversation
Public repos cannot run the org-level gitleaks ruleset workflow (it lives in a private repo), so this repo carries its own copy using the upstream gitleaks/gitleaks-action v3 (SHA-pinned) with the public-repo license key. The job name gitleaks-scan matches the required check context used org-wide, replacing devsec/jenkins/gitleaks/leak-scan. Part of the DevSec Jenkins cleanup; canary proven on stats_plug (#19, detection test #20).
mikhailbahdashych-glia
requested review from
KristinaNa
and removed request for
a team
September 1, 2026 14:48
anna-agafonova
approved these changes
Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the Jenkins leak-scan with
gitleaks-scanon this public repoPart of the org-wide DevSec Jenkins cleanup — canary proven on stats_plug (clean run: salemove/stats_plug#19; planted-secret detection: salemove/stats_plug#20).
gitleaks/gitleaks-actionv3.0.0, SHA-pinned;actions/checkoutv6 SHA-pinned; explicit minimal permissions; org secretGITLEAKS_LICENSE_PUBLIC(already scoped to this repo).gitleaks-scandeliberately matches the required-check context private repos already use — after all 14 public repos carry this workflow, ghom swaps the required check fromdevsec/jenkins/gitleaks/leak-scantogitleaks-scanand the Jenkins scan retires..deployignoreexists in this repo (library class, no deploy-trigger mechanism) — checked, nothing to update.This PR itself runs the workflow — the
gitleaks-scancheck below should appear and pass.