You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that using the github subcommand without providing a --token only checks public repos. This works well for me because I'm specifically searching for leaked secrets in public repos. However, I want to automate this process using GitHub Actions, scheduling scans every week or so. The issue is, if I do this, I'll end up with the same results each time, which just creates unnecessary noise. Plus, using --since-commit isn't achievable by design.
Preferred Solution
I suggest adding support for --after-date to scan for leaked secrets in commits made after a specified date, making it easier to integrate into CI/CD pipelines. This way, I can save the date of the last scan and use it for the next one.
Additional Context
Implementing this feature would simplify the CI/CD setup and ensure more effective scanning by avoiding redundant results.
References
The text was updated successfully, but these errors were encountered:
Please review the Community Note before submitting
Description
I've noticed that using the
github
subcommand without providing a--token
only checks public repos. This works well for me because I'm specifically searching for leaked secrets in public repos. However, I want to automate this process using GitHub Actions, scheduling scans every week or so. The issue is, if I do this, I'll end up with the same results each time, which just creates unnecessary noise. Plus, using--since-commit
isn't achievable by design.Preferred Solution
I suggest adding support for
--after-date
to scan for leaked secrets in commits made after a specified date, making it easier to integrate into CI/CD pipelines. This way, I can save the date of the last scan and use it for the next one.Additional Context
Implementing this feature would simplify the CI/CD setup and ensure more effective scanning by avoiding redundant results.
References
The text was updated successfully, but these errors were encountered: