Instructions how to prepare a new release #617
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
NissesSenap
force-pushed
the
prepare_release
branch
2 times, most recently
from
4470436
to
ce77bf6
Compare
HVBE
previously requested changes
Nov 23, 2021
Co-authored-by: Hubert Stefanski <35736504+HubertStefanski@users.noreply.github.com>
Co-authored-by: Hubert Stefanski <35736504+HubertStefanski@users.noreply.github.com>
Co-authored-by: Hubert Stefanski <35736504+HubertStefanski@users.noreply.github.com>
|
And it's great that you are :) |
|
The prepare documentation also points towards: #624 |
pb82
reviewed
Nov 26, 2021
NissesSenap
dismissed
HVBE’s stale review
Want to merge this, I assume it's okay :)
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.
Description
This is mainly fur the maintainers so we have a standard way of preparing new releases.