Auto generate release notes #529
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
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 PR adds a
release.ymlfile to the repo that automatically will generate release notes based on the keep a changelog standard we maintain at Laravel.These new labels will need to be added to the repo for this to work (I'll add them once this PR gets merged):
And all PR's will need to be labeled in the future in order to make this work properly. PR's that weren't labeled or weren't in a label that matches the given categories will be moved under "Changed".
In general, this will save much more time when generating release notes. Let's try this out as a test case on Octane before rolling it out on other repos.