release_drafter: add basic config and template for releases #257
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
Contributor
Author
|
I wonder what category/label this request would be best suited to...perhaps a |
jphines
approved these changes
Oct 10, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
Creating and publishing a release right now is a very manual task that can, depending on the amount of merges, take a considerably long time to prepare.
We'd like to improve this workflow to not only make it less time consuming when releases are worked on, but to help encourage more frequent releases as required by making the overall process easier. This change focuses on the actual creation of a release draft.
Solution
By using https://github.com/toolmantim/release-drafter, we can largely automate the process of formulating a release draft by having it automatically and continuously populate a draft as and when pull requests are merged.
Notes
The draft that this creates is slightly different to what we've been using in the past, however I think this should work fine instead! (it might require some tweaks along the way)