Updated Copyright to IBM Headers#170
Merged
Merged
Conversation
ritikrajdev
reviewed
Nov 18, 2025
| # files or folders should be ignored | ||
| header_ignore = [ | ||
| "**/testdata/**", | ||
| "licensecheck/copyright_test.go", |
Collaborator
Author
There was a problem hiding this comment.
It is a test file which contains old Hashicorp tests only. The code will replace all the cases and it might break the existing tests that are not relevant to the changes done for IBM Copyright and hence we are ignoring this file from header update.
If we keep the header, then we will have to manually change header every year, and hence the header from that file itself is removed.
ritikrajdev
approved these changes
Nov 19, 2025
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
🔗 External Links
https://hashicorp.atlassian.net/browse/IND-4227
👍 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.