update year of birth docs for 2025 #798
Open
Conversation
This file contains 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
This part of the readme is currently accurate but seems it will go out of date on January 1st, 2025. I am committing this approx 13 days in advance to prepare for the new year.
ChrisLovering
approved these changes
Dec 19, 2024
|
This can be merged now that the year is 2025. |
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.
Summary
This part of the readme is currently accurate but seems it will go out of date on January 1st, 2025. I am committing this approximately 13 days in advance to prepare for the new year.
This change should not be merged before the year 2025 begins. I would recommend merging on January 1st, perhaps sometime after the last time zone ticks to 00:01 (1 minute after midnight) on January 1st, 2025, this will help ensure that these docs do not result in any confusion prior to them becoming accurate.
Testing
Please not that I have not tested/confirmed these changes locally, though I believe this example should be simple enough that manual testing is not necessary.