Skip to content

ci: add secret scanning on pull requests #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

Closed
guiddeco-idans-claude wants to merge 1 commit into from
Closed

ci: add secret scanning on pull requests #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
24 changes: 24 additions & 0 deletions .github/workflows/secret-scanning.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
name: 'Secret Scanning'

on:
pull_request:

@overcut-ai overcut-ai Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[major]: Using pull_request can prevent repository secrets from being available on runs originating from forks, which may cause this org-wide secret scanning workflow to silently lose coverage on external contributions. If the reusable workflow is designed for safe read-only execution, consider using pull_request_target (with strict checkout/ref handling) or explicitly document that forked PRs are out of scope.

branches:
- main
- master
- develop

permissions: {}

concurrency:
group: secret-scanning-${{ github.ref }}
cancel-in-progress: true

jobs:
secret-scan:
name: 'Scan for secrets'
uses: guiddeco/shared-workflows/.github/workflows/ci-secret-scanning.yaml@v1
permissions:
contents: read
pull-requests: write
with:
fail_on_findings: false