Closed
Conversation
This was referenced Dec 28, 2024
c19f258 to
024037e
Compare
Contributor
|
A PR preview is available: Preview URL |
1 similar comment
Contributor
|
A PR preview is available: Preview URL |
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.
Internal Notes for Reviewers
Demonstration of the functionality added in #607 and #610.
Year end cleanup
Try it yourself
gh pr checkout 611release-scripts/year-end-cleanup.ipynb.2025when the year input dialogue prompts you.2025-releases.qmdpage created with the moved releases as listings2025in "About > Releases"_quarto.ymlthe# CURRENT-YEAR-END-MARKERwill be moved to above your 2025 releases but BELOW the fake 2026 releaserelease-scriptsfolderGenerate release notes
I ran the new release notebook and Make command.
index.qmdand got rid of the oldest release making the section uniform!