Remove date from all copyright statements#162
Merged
Mike Hobson (mike-hobson) merged 2 commits intoMetOffice:mainfrom Oct 24, 2025
Merged
Remove date from all copyright statements#162Mike Hobson (mike-hobson) merged 2 commits intoMetOffice:mainfrom
Mike Hobson (mike-hobson) merged 2 commits intoMetOffice:mainfrom
Conversation
Collaborator
|
Would it be appropriate to create a unique copyright file and include that file at the top instead of repeating the text in many places? .. include:: copyright.rst |
Mike Hobson (mike-hobson)
approved these changes
Oct 24, 2025
Contributor
Mike Hobson (mike-hobson)
left a comment
There was a problem hiding this comment.
Scrollathon!
It all looks good to me. Just the removal of the dates and one change to the advice.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Remove the year from all copyright statements, and update the style guide appropriately.
Linked issues
Closes # (issue)
Developer tags
Type of change
How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Checklist:
Reasoning on why any of the above boxes have not been checked
Documentation change only.
Review Checks (To be filled in by the reviewer/s)