Update copyright year to 2022 #4086
Merged
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
raboof
force-pushed
the
update-copyright-to-2022
branch
2 times, most recently
from
1b45848 to
01fabbb
Compare
raboof
force-pushed
the
update-copyright-to-2022
branch
from
01fabbb to
a52c837
Compare
jrudolph
approved these changes
Mar 24, 2022
Contributor
jrudolph
left a comment
jrudolph
left a comment
There was a problem hiding this comment.
LGTM
Didn't we change the headers in some projects to use a version without the current year?
Contributor
Author
Hmm, I don't know - I'd be in favor but I'm not sure what the reason for having the year is. I see 2021 in most repo's tbh... |
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.
No description provided.