gitleaks / gitleaks/gitleaks-action

Problem when adding workflow_dispatch

Open
#124 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
644
Forks
194
PR merge metrics
No merged PRs in 30d

Description

I'd like this action to scan for more than just the last commit, so I forked it to scan all code (not commits). After adding a new action, I wanted to create a selection for users to select via input:
'last_commit' - Scan the last commit
'whole_repo' - Scan the entire repository

When I use workflow_dispatch with this selection, the main action scans all commits, so previous leaks are detected and the action fails every time.

Is this the expected behavior of this action?
Is it possible to configure this action to scan code, not commits?

Contributor guide

Open the contributing guide

Research direction

Start with the workflow_dispatch input selection and the main action entry point, reproducing the last_commit and whole_repo cases described in the issue. Determine whether the action scans commits or repository contents for each selection; done means the intended scope is established and the behavior is either corrected or clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
ci-cd, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.