Skip to content
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

Trigger release drafter updates on non-PR commits on default branch #1344

Open
awinecki opened this issue Jun 6, 2023 · 1 comment
Open

Comments

@awinecki
Copy link

awinecki commented Jun 6, 2023

Is it possible to trigger release drafter on each commit on git default branch (e.g. master or main)?

Here's my reasoning and potential use case for this.

I would like to create a flow similar to https://trunkbaseddevelopment.com/, where:

  • Anyone can commit on main branch,
  • 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:

screen-2023-06-06 at 13 47 30@2x

And subsequent commits did not re-trigger release drafter.

@darioblanco
Copy link

darioblanco commented Aug 16, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants