Automated workflow for semantic releases

[mrcjkb]

Does this feature exist in Emacs orgmode core?

N/A

Orgmode link

No response

Feature value

The last release is a few months old. It would me nice if new releases with fixes could be published more frequently.
Since you already use conventional commits, perhaps an automated workflow with the release-please-action would make it easier to publish releases more frequently?

Additional context

I'd be happy to contribute a workflow if you're open to it 😄

[ficcdaf]

I support this certainly. Release-please is very easy to set up.

[kristijanhusak]

Yeah, we can add this, just please set it up as a workflow_dispatch. I don't want to make a new release on every push to master branch.

[ficcdaf]

Yeah, we can add this, just please set it up as a workflow_dispatch. I don't want to make a new release on every push to master branch.

I have release-please set up on my own plugin Ashen. The way it works is when you push commits to main, it processes them (according to conventional commit standards) and automatically creates both a change log and determines the semver number for the next release.

Crucially, all it does is create a PR and manage that PR (keeping it updated with new pushes to main). To actually publish a release, all you need to do is merge that PR. The only file actually modified in the PR is the changelog file. When you merge it, the action creates a GitHub release.

So, it only actually creates a new release and updates the changelog in main when you merge the release-please PR.

In this case, is a workflow dispatch still necessary? I don't actually know what that is, sorry. Is this something you'd like me to set up and submit a PR?

[kristijanhusak]

workflow_dispatch is basically a button in the actions that will trigger the workflow.

The PR solution is also ok, so you can go with that if you want.

[ficcdaf]

OK, should I also add a note under the contribution guidelines to please use conventional commits?

[kristijanhusak]

Yeah, you can do that. Set up a PR and we can discuss any necessary details there.

[mrcjkb]

OK, should I also add a note under the contribution guidelines to please use conventional commits?

I would suggest a checklist in a PR template.
If you squash merge PRs, it's enough for the PR title to have a conventional commit prefix.

[ficcdaf]

I created the PR. I don't know how to request a review on it (or if that's something I'm supposed to do?) I'm still new to this contributing thing.

Anyways, I added the workflow, added a PR template, and updated contributing.org. Let me know if I should change anything!