Is your feature request related to a problem? Please describe.
The process to create new releases in this GitHub repository is manual and need to be automated.
The rationale is that a continuous delivery process needs the smallest possible increments to allow testing of new changes as they are merged. The current manual process often results in the bundling of multiple patches into a single release, making harder to isolate eventual problems during testing.
Describe the solution you'd like
Support an annotation in issues, pull requests, and comments, from select team members, to automatically create a new GitHub release with the changes. The annotation should include the suggested bump in terms of semver. E.g. "patch", "minor", "major".
Edit on 2/13/23: Adopted the Semantic Release package to implement this feature, so every code merge to main is running the release process. It makes automatic determinations about minor/patch releases based on the prefix of commits, such as fix and feat. If it finds any commit with a prefix of feat, than it creates a minor release, otherwise it creates a patch release. Major releases need to be created manually via GitHub UI.
Describe alternatives you've considered
Off-the-shelf annotation engines based on GitHub.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. The process to create new releases in this GitHub repository is manual and need to be automated.
The rationale is that a continuous delivery process needs the smallest possible increments to allow testing of new changes as they are merged. The current manual process often results in the bundling of multiple patches into a single release, making harder to isolate eventual problems during testing.
Describe the solution you'd like Support an annotation in issues, pull requests, and comments, from select team members, to automatically create a new GitHub release with the changes. The annotation should include the suggested bump in terms of semver. E.g. "patch", "minor", "major".
Edit on 2/13/23: Adopted the Semantic Release package to implement this feature, so every code merge to
main
is running the release process. It makes automatic determinations about minor/patch releases based on the prefix of commits, such asfix
andfeat
. If it finds any commit with a prefix offeat
, than it creates a minor release, otherwise it creates a patch release. Major releases need to be created manually via GitHub UI.Describe alternatives you've considered Off-the-shelf annotation engines based on GitHub.
Additional context Add any other context or screenshots about the feature request here.