Repository navigation
Conversation
(It will be modernised and added to a README.)
for more information, see https://pre-commit.ci
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.
References and relevant issues
Relevant previous discussion is in Zulip.
Description
This PR proposes moving the release notes generation from a separate repo to
this one. The motivation is as follows:
napari/napari-release-tools and the full documentation update in this repo.
need to be backported to the additional notes in the docs repo.
specify the output directory, which is different for each release manager, so
it can't be generalised in the script.
Moving the tooling and notes here makes it easier to keep everything in sync,
and also allows the script to have default values for the file paths, and it
then becomes easier to run with
uv run tools/generate_release_notes.py <milestone>and no further arguments.
See the new README for more details.