GitGuardian Can Update Pull Requests With GitHub Check Runs
Did you know that GitGuardian can add comments directly to your GitHub pull requests and even stop a PR from succeeding if it contains any hardcoded secrets?
Did you know that GitGuardian can addÂ
comments directly to your GitHub pull requests and even stop a PR from succeedingÂ
if it contains any hardcoded secrets? The GitHub API makes it possibleÂ
for the GitGuardian App to run powerful checks against all theÂ
code changes in a repository. When a new pull request is created,Â
a new check run is performed, and GitGuardian will scan through each commitÂ
inside the PR, not just the most recent one. If someone added a secret to an early commit,Â
but then removed it right before making the PR, you still need to know it is present inÂ
the git history so you can address it. Activating or deactivatingÂ
the GitGuarian check run is easy. Once you have the GitGuardian appÂ
installed on GitHub from the marketplace, navigate to your GitGuardianÂ
Dashboard, and click on Settings. Next click on Integrations and then theÂ
Edit button beside the GitHub Listing. In this GitHub integration menu, scrollÂ
down to the "Check runs" section. From here you can toggle the featureÂ
"Automatically post a comment on pull requests when a check run detectsÂ
an incident", either on or off. You also have the option to configure the checkÂ
run to be blocking, causing the PR to fail, thereby protecting your pipeline,
or non-blocking, reporting incidents as Neutral, allowing pull requstsÂ
with incidents to move ahead. GitGuardian is here to help keep everyoneÂ
safe as you work to move your code, but not your secrets, toward production.