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.