gitleaks / gitleaks/gitleaks-action
Recommendation on workflow setup for PRs
- Dominant language
- JavaScript
- Stars
- 644
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I would like to know if you have any recommendation on how to setup this action to make it work with pull requests from a fork ?
For example, in my repository it always fail with "*** is an organization. License key is required.", see [here](https://github.com/CExA-project/ddc/actions/runs/20260028897/job/58169837550). I added the key both to my organization and the repo. My configuration is the following:
```
gitleaks-scan:
name: gitleaks
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
with:
fetch-depth: 0
- uses: gitleaks/gitleaks-action@ff98106e4c7b2bc287b24eaf42907196329070c7 # v2.3.9
env:
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
GITLEAKS_LICENSE: ${{secrets.GITLEAKS_LICENSE}}
```
Contributor guide
Research direction
Start with the workflow configuration in the issue and inspect the linked GitHub Actions run for the fork pull request failure. Determine what setup guidance is needed for this action and define done as a documented, verified recommendation or example that explains the required behavior for forked pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100