You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optionally, people create PRs to request code review.
In an experienced team (possibly using Foreman-style commit checking), you don't always need to enforce PRs for every small change, as it may slow you down. Often a small change in README.md is just a quick commit to main.
However, it would still be great to use a tool like release drafter and see such commits in the release changelog.
An example commit message triggering this would be:
feat[PROJ-123] update README.md with deployment instructions #patch
This should trigger release drafter, adding a patch to the changelog.
—
Current flow as per my testing:
I've pushed a single commit to main and it created a new release draft, but with NO CHANGES annotation:
And subsequent commits did not re-trigger release drafter.
The text was updated successfully, but these errors were encountered:
I did create https://github.com/darioblanco/release-wizard a long time ago but it did not have much adoption. It actually adrdesses problems like this, has trunk based development support and even can run in monorepos.
I came back to release drafter because I would love to use a tool with more adoption and I still see that this is sadly not possible.
If release-wizard helps you with your problem I might consider to give it some support, as I do not think that release-drafter will address this problem soon, I also checked the code base and the change did not seem so trivial to implement.
Is it possible to trigger release drafter on each commit on git default branch (e.g.
master
ormain
)?Here's my reasoning and potential use case for this.
I would like to create a flow similar to https://trunkbaseddevelopment.com/, where:
main
branch,In an experienced team (possibly using Foreman-style commit checking), you don't always need to enforce PRs for every small change, as it may slow you down. Often a small change in README.md is just a quick commit to
main
.However, it would still be great to use a tool like release drafter and see such commits in the release changelog.
An example commit message triggering this would be:
This should trigger release drafter, adding a
patch
to the changelog.—
Current flow as per my testing:
I've pushed a single commit to
main
and it created a new release draft, but with NO CHANGES annotation:And subsequent commits did not re-trigger release drafter.
The text was updated successfully, but these errors were encountered: