Move header copyright from 2025 to 2026#300
Conversation
Signed-off-by: kangclzjc <kangz@nvidia.com>
renormalize
left a comment
There was a problem hiding this comment.
I don't think we should have to update the year in the license for the generated files every year. The rest of the ecosystem does not do this either.
There seems to be a gap in the add-license-headers target which is causing this diff in the generated files.
Ya, we'd just add 2026 to new files. |
|
No problem, I add this because I see that CI/CD can't pass the check |
|
Turns out it was Generated files had |
What type of PR is this?
CI/CD will check the header and compare the year.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a API change?
Additional documentation e.g., enhancement proposals, usage docs, etc.: