Skip to content
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

Updated current year to 2023 #128

Merged
merged 1 commit into from
Jan 30, 2023
Merged

Updated current year to 2023 #128

merged 1 commit into from
Jan 30, 2023

Conversation

quaat
Copy link
Contributor

@quaat quaat commented Jan 26, 2023

Description:

Type of change:

  • Bug fix.
  • New feature.
  • Documentation update.

Checklist for the reviewer:

This checklist should be used as a help for the reviewer.

  • Is the change limited to one issue?
  • Does this PR close the issue?
  • Is the code easy to read and understand?
  • Do all new feature have an accompanying new test?
  • Has the documentation been updated as necessary?

@quaat quaat linked an issue Jan 26, 2023 that may be closed by this pull request
@quaat quaat requested a review from CasperWA January 26, 2023 14:01
Copy link
Contributor

@CasperWA CasperWA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine.

Should we set up some form of automation of this, or just leave this as a once-a-year task, eventually showing when we stop caring about the repository?

@CasperWA CasperWA merged commit e782018 into master Jan 30, 2023
@CasperWA CasperWA deleted the 127-update-current-year branch January 30, 2023 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update current year
2 participants