-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update copyright to 2022 - automate this? #4532
Comments
Related Issue #3979 Will look into automating this. Any suggestions are welcome |
US copyright law: https://copyright.gov/title17/title17.pdf A related question seems to indicate maybe this doesn't necessarily have to be updated |
Will write a little tool to automate this. |
I've got an npm script to do this here: |
@scottbell can you write test instructions here? |
To test, run the script and ensure neither the string 2020 nor 2021 exist in the codebase. Also check through git diff that only copyrights we’re affected. |
Testathon 2022-01-24 The script is working as expected, though on the The script will need to be rerun to resolve an older copyright on the following files: |
@scottbell can you take a look? |
Ah, these were all modified/added after the previous PR. @unlikelyzero how do you want to handle this going forward? |
@scottbell can you make another PR against release/1.8.4 with those changes? I'm not sure if we need to automate this any further. This was likely just a case of a bad backmerge, right? |
https://github.com/nasa/openmct/pull/4775/files Yeah, this was caused by people creating new files before my PR went in. It should happen less and less. |
Verified Fixed in Testathon on 01/26/22 - All files referenced were updated |
Copyright for openmct files needs to be updated to 2022 (when 2022 comes around).
If possible, this should be automated.
The text was updated successfully, but these errors were encountered: