Add Automatic Drafting of Release Notes #3462
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
|
Why is the release drafter breaking? |
|
The release-drafter build will fail in this PR because there is no release-drafter.yml file checked into the main branch yet. |
|
Is the versioning story OK? |
|
cc @PascalSenn |
|
Looks good to me :) Thanks for putting this together! |
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.
The releases created by this repo have no information in them about what PR was completed. This PR adds release-drafter which automatically drafts release notes but does require you to use the following GitHub labels on your PR's:
Apply one or more of the following to determine the heading the PR will come under:
🧰 maintenanceis a new label that will need to be created. I find this label useful for miscellaneous PR's that don't fit under any other category.You can also apply the following labels (which would need to be created) which automatically increments the major, minor or patch version number in the draft release. I'm not sure you need this part since I'm not sure how you do versioning.
For a full walkthrough of how all this works, you can check out my blog post:
https://rehansaeed.com/the-fastest-nuget-package-ever-published-probably/
BTW, the release-drafter build will fail in this PR because there is no release-drafter.yml file checked into the main branch yet.