-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document release process #118
Document release process #118
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for setting this up @Potherca !
I've got a few questions and other than that, just some small grammar/punctuation nitpicks. Please see my remarks inline.
Note: I haven't tested the script.
@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 <[email protected]>
- 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. |
6559199
to
a9990e9
Compare
This MR documents the basic steps required to create a new release in the contributing file.
It also add
github_changelog_generator
setting file and a script to run the changelog generator.Closes #114