ci: Add workflow to auto-create release notes#270
Merged
daniele-moro merged 3 commits intomainfrom Jun 13, 2025
Merged
Conversation
1b800c1 to
cf8666b
Compare
cjnolan
approved these changes
Jun 12, 2025
Contributor
cjnolan
left a comment
There was a problem hiding this comment.
Looks great! Is there a way to make this a common workflow in orch-ci that workflows in each repo can then call when a new tag is added, as is done with the pre and post workflows?
Contributor
Author
I was thinking about it. I want to run it few times here, then I can move it to orch-ci. |
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
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.
Description
Trigger workflow on tags to automatically create GH releases with proper release notes based on the changes that applies to the subfolder referred by the release.
Any Newly Introduced Dependencies
Please describe any newly introduced 3rd party dependencies in this change. List their name, license information and how they are used in the project.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: