Create release issue template #186
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
Co-authored-by: Jaclyn Taroni <[email protected]>
|
Okay, I incorporated the suggestion for the changelog checkbox. This should be ready for another look @jaclyn-taroni. |
|
I'm going to merge this so I can use it! |
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 #175
This PR adds a new issue template with a checklist for releases. I used a similar format to the release template that we have in
scpca-nf. I also tried to add some instructions to help if people are only releasing part of the updates that are present indevelopment, especially because we are about to do that. Please check to make sure the instructions and additional comments are clear.One thing that I didn't do was add a version tag in the issue title. We have that for other release checklists, but here the tag is based on the day the docs get released. So instead, I added a note about updating the title to include the expected contents of the release. If others feel strongly about including the version tag in the title, then I can add that back in.