We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Similar to BCDA-APS/apstools#921 and nexusformat/definitions#1355, update the project's copyright notices to the current year.
Do this in a branch with a PR.
The text was updated successfully, but these errors were encountered:
Using murky's update_copyright_date:
update_copyright_date
(murky) prjemian@arf:~/.../BCDA-APS/gemviz$ update_copyright_date -v . UChicago Update with 3 line(s) changed: /home/prjemian/Documents/projects/BCDA-APS/gemviz/.pytest_cache/v/cache/nodeids Update with 1 line(s) changed: /home/prjemian/Documents/projects/BCDA-APS/gemviz/gemviz/LICENSE Update with 1 line(s) changed: /home/prjemian/Documents/projects/BCDA-APS/gemviz/gemviz/__init__.py Update with 1 line(s) changed: /home/prjemian/Documents/projects/BCDA-APS/gemviz/gemviz.egg-info/PKG-INFO
Sorry, something went wrong.
DOC #209
759954d
MNT #209 add opyrights to other Py files
60de48a
MNT #209 per ruff (identical with other PRs)
4ce118d
STY #209 per 'black'
9feb7fd
prjemian
Successfully merging a pull request may close this issue.
Similar to BCDA-APS/apstools#921 and nexusformat/definitions#1355, update the project's copyright notices to the current year.
Do this in a branch with a PR.
The text was updated successfully, but these errors were encountered: