-
Notifications
You must be signed in to change notification settings - Fork 1
feat: [PTF-1962] CI-based post- main-branch-merge auto-release/versioning #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR introduces automated release and versioning triggered by commits to the master branch. The changes enable CI-based auto-release using Conventional Commits semantics to eliminate manual tagging and improve consumption of the library.
Key changes:
- Changed workflow trigger from
pull_requesttopushto enable post-merge automation - Added a new
releasejob that creates tags and GitHub releases automatically for master branch commits (excluding those prefixed with "no-release:")
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
2795873 to
eb2584b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Motivation
Ease maintenance. Ease consumption.
Description
By auto-versioning based on Conventional Commits -like semantics we prevent having to remember to release for each update that is not
no-release. We also make it easier to consume for all releases, instead of having to target SHAs sometimes, when a tag is missing.