no-issue: PR template for releases #5270
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
|
After merging, I’ll add a bookmark to the big ugly link to the releases Slack channel (Probably somewhere appropriate in Slab too) |
edmofro
requested changes
Dec 11, 2023
suggests not to use leading 0’s
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.
Changes
Created a PR template for releases. After merging, this can (in theory) be invoked using https://github.com/beyondessential/tupaia/compare/master...dev?quick_pull=1&title=Release+20yy-w&labels=release&template=release_template.md, which will also automatically add the release tag.
If an open
master←devPR already exists, GitHub will prompt you to view that one instead of creating a new one.The existing pull request template remains the default. Unfortunately, this needs to stay at the top level of the
./githubfolder; moving it into the new./github/PULL_REQUEST_TEMPLATEfolder makes it accessible only via a link with atemplatequery parameter (like the one above).Testing
This can’t be comprehensively tested until it’s merged into the default branch. Instead, I replicated this template setup in a private repo on my own account, and it seems to work there
Screenshots
None.