ci: drop the redundant gitleaks secret-scan job - #84
Merged
Conversation
GitHub native secret scanning and push protection are both enabled on this repo (public, where both are free), so gitleaks duplicated coverage the platform already provides. This job was passing -- it used the free gitleaks docker CLI, not the license-gated gitleaks-action. Removing it reduces CI surface rather than fixing a failure. NOTE: "Secret Scan" is currently a required status check in the active "Protect main" ruleset. That context must be dropped from the ruleset, or this PR cannot merge and later PRs will block on a check that never reports.
jmagar
enabled auto-merge (squash)
July 29, 2026 02:12
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
1 participant
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.
GitHub native secret scanning and push protection are both enabled on this
repo (public, where both are free), so gitleaks duplicated coverage the
platform already provides.
This job was passing -- it used the free gitleaks docker CLI, not the
license-gated gitleaks-action. Removing it reduces CI surface rather than
fixing a failure.
NOTE: "Secret Scan" is currently a required status check in the active
"Protect main" ruleset. That context must be dropped from the ruleset, or this
PR cannot merge and later PRs will block on a check that never reports.