Skip to content

Name the gitleaks step for the range it actually scans #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bezilla merged 1 commit into from
Sep 6, 2026
Merged

Name the gitleaks step for the range it actually scans #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,12 @@ jobs:
- uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5.1.0
with:
fetch-depth: 0
- name: gitleaks over full history
# Named for what it does. The action scans the commit range of the
# event -- one commit on a pull request, the pushed range on a push --
# not the whole repository; fetch-depth: 0 makes that range resolvable,
# it does not widen it. Full history is covered by the identity job,
# which runs the pre-push gate in its --all-history mode.
- name: gitleaks over the pushed range
uses: gitleaks/gitleaks-action@ff98106e4c7b2bc287b24eaf42907196329070c7 # v2.3.9
env:
# The action refuses to scan a pull_request event without this and
Expand Down
Loading