Document the release process #661
Merged
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
intgr
commented
Sep 11, 2024
CONTRIBUTING.md
Outdated
Comment on lines
121
to
122
| - Delete all release notes lines containing `by @pre-commit-ci` or `by @dependabot`, as these are | ||
| irrelevant for our users. |
There was a problem hiding this comment.
It's an additional manual step, but IMO release notes are too noisy if these are included.
Co-authored-by: sobolevn <mail@sobolevn.me>
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.
This is my vision of what the release process looks like after release automation (#660) is merged.
Once we reach agreement here, I will also open a similar PR for
django-stubs.See rendered Markdown here.
Related issues