New env var GITLEAKS_ADDITIONAL_COMMENT to add e.g. a custom docs link
#164
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… a custom docs link
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We'd like to add a custom docs link to the Gitleaks PR comment that could help users to understand what happened and what should they do now etc. We have a page written so we'd like to add a link only, or a short text with a link or something like that, we can use markdown so the options are pretty flexible.
This PR adds a new env var
GITLEAKS_ADDITIONAL_COMMENTthat would simply be appended to the main message body, before the "cc notify_users" line.