Add headers default ignore patterns (composite GitHub Actions + .git)#193
Open
radeksimko wants to merge 2 commits intohashicorp:mainfrom
Open
Add headers default ignore patterns (composite GitHub Actions + .git)#193radeksimko wants to merge 2 commits intohashicorp:mainfrom
.git)#193radeksimko wants to merge 2 commits intohashicorp:mainfrom
Conversation
ritikrajdev
reviewed
Feb 13, 2026
radeksimko
force-pushed
the
add-headers-default-ignore-patterns
branch
from
133ee24 to
b951c49
Compare
Member
Author
|
@ritikrajdev I updated the PR as per feedback and also added links to the description for more context - please take another look. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
🛠️ Description
This is to reduce noise, and avoid the need to add these relatively common paths into the configuration.
References:
🔗 External Links
👍 Definition of Done
🤔 Can be merged upon approval?
✅
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.