chore: update copyright headers script and add missing headers #207
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
Signed-off-by: Marin Maksutaj <[email protected]>
|
eherozhao
approved these changes
May 26, 2025
npmacl
approved these changes
Sep 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What was the problem/requirement? (What/Why)
The copyright headers script needed improvements to handle more file types and to work more efficiently. Additionally, we needed a test to verify that all files have proper copyright headers.
What was the solution? (How)
Enhanced the add_copyright_headers.sh script. Also updated the test_copyright_headers.py file to verify all files have proper headers.
What is the impact of this change?
Ensures all files have proper copyright headers and provides a test to verify compliance. This improves our code quality and legal compliance.
How was this change tested?
Ran the full test suite including the new copyright headers test. All tests passed successfully.
Please run the integration tests and paste the results below
Was this change documented?
Yes, the changes are self-documenting in the code and the test file.
Is this a breaking change?
No, this is not a breaking change. It only adds copyright headers and improves the script that adds them.