#50: Described release process in Developer Guide #52
Conversation
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
kaklakariada
requested changes
May 22, 2024
Co-authored-by: Christoph Pirkl <[email protected]>
kaklakariada
previously approved these changes
May 22, 2024
ahsimb
reviewed
May 22, 2024
| ``` | ||
|
|
||
| Nox session `prepare-release` will | ||
| * Create a branch, e.g. `prepare-release/1.2.3` starting from `main` |
Contributor
There was a problem hiding this comment.
I think, in this case, we should be in the main branch locally.
kaklakariada
approved these changes
May 22, 2024
ahsimb
approved these changes
May 22, 2024
ckunki
deleted the
doc/#50-Added_section_Add_how_to_release_to_Developer_Guide
branch
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.
Closes #50