-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update license 2024 #419
base: main
Are you sure you want to change the base?
Update license 2024 #419
Conversation
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I seem to remember @jurgenvinju had good reasons not to do this.
So if you want to propose this, we should understand what it means to change the year of files that haven't been touched in 2024.
Ok, I am interested in that reasoning. This PR was triggered by the fact that @rodinaarssen commented on the outdated years in new files in a different PR (#397). I had a look and saw that last year, many filles (either touched in 2023 or not) were updated. |
Okay, let's wait for @jurgenvinju to get back from holiday (and me as well). There were reasons, I forgot them. I just accidentally got an email alert where I noticed the title, apart from that, I'm not checking stuff much ;) |
Update the license header template, and apply it to all headers.