Skip to content

chore: tighten organization gitleaks workflow #1

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
BreakableHoodie merged 1 commit into from
Nov 14, 2025
Merged

chore: tighten organization gitleaks workflow #1

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
1 change: 0 additions & 1 deletion .github/workflows/gitleaks.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,6 @@ on:
workflow_dispatch:

permissions:
actions: write
contents: read
pull-requests: write
Comment on lines 8 to 10
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore actions write permission for artifact upload

The workflow token no longer requests actions: write, but the “Upload redacted report” step uses actions/upload-artifact@v4 to create an artifact. GitHub requires actions: write on GITHUB_TOKEN for artifact uploads; without it the step will return 403 and the job will fail whenever findings exist, defeating the stated goal of keeping the scan non‑blocking. Consider keeping read-only scopes elsewhere but still requesting actions: write or otherwise skipping the upload.

Useful? React with 👍 / 👎.


Expand Down
Loading