Document release process #118
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
|
@jrfnl I finally managed to find some time to go through your feedback. I think I got it all, could you check at your convenience? |
Co-authored-by: Juliette <663378+jrfnl@users.noreply.github.com>
- Make footnote markers a link to the footnotes section - Mention that either generate command needs to be run from the project root - Mention that the `.sh` script required BASH to run - Fix Code of Conduct link
|
I'm going to merge this, to keep things moving. |
Potherca
force-pushed
the
issues/114-release-process
branch
from
6559199
to
a9990e9
Compare
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 MR documents the basic steps required to create a new release in the contributing file.
It also add
github_changelog_generatorsetting file and a script to run the changelog generator.Closes #114