Repository navigation
Fold the docs work into 0.7.5 for distribution - #245
Merged
Merged
Conversation
The README restructure, the second de-lecturing pass and the six documentation defects were sitting in [Unreleased] behind an already-tagged 0.7.5. Folded into the [0.7.5] section so what gets distributed as v0.7.5 is the tree people will actually read, rather than a release whose README improves only on main. Ordered chronologically within Documentation rather than newest-first, because the second README pass explicitly refers back to the first. No version bump: this is the same release, re-cut. setup.py, chorus/__init__.py and CITATION.cff stay at 0.7.5, and the [0.7.5] compare link is unchanged. The tag and GitHub Release move with this commit, which means the four traps from the v0.7.3 move all apply again: delete without -q and check the exit code, recreate with --cleanup=verbatim and count the '#' headings back, restore isDraft=false because deleting a tag with a Release demotes it to a draft, and regenerate both copies of the notes from the one CHANGELOG section and hash-compare them. Fast suite 2,144 passed / 35 skipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The README restructure, the de-lecturing pass and the six documentation defects were sitting in
[Unreleased]behind an already-tagged 0.7.5 — so the release you distribute would have had the oldREADME while
mainhad the good one. Folded into the[0.7.5]section.setup.py,chorus/__init__.pyandCITATION.cffstay at0.7.5; the
[0.7.5]compare link is unchanged.refers back to the first.
Once this merges, the tag and GitHub Release move to the new commit, which re-runs all four traps from the
v0.7.3 move: delete without
-qand check the exit code, recreate with--cleanup=verbatimand count the#headings back, restoreisDraft=false(deleting a tag with a Release demotes it to a draft), andregenerate both copies of the notes from the one CHANGELOG section and hash-compare.
Fast suite 2,144 passed / 35 skipped; integration re-running for the re-cut.