Shameless plug, I suggest a workflow very similar with my own github action, https://github.com/rubenfiszel/autochangelog-action. The suggested workflow is to:
- trigger the action through CURL
- the action generates a changelog diff and some
manifest file diff with the version change (such as package.json).
The next version is inferred using semantic versioning and
conventionnal commits, respecting fix, feat and breaks.
With that new content, you generate a PR.
That PR is labeled with "autorelease"
- When that PR is merged, another action is triggered wich do the
Github Release and fill the body with the changelog diff
I'm one of the people building:
A GitHub App that lets you trigger your Actions without needing to run cURL
Do you know what could be the issue?
The semantic release tooling is so good, I've started using it on non-js projects. I'm using it to manage Terraform modules, base docker images, etc. Once you're doing that, might as well mix in Husky and commit-lint to manage your git hooks and commit messages too.
There are comparable things elsewhere, but node is so ubiquitous in my tool chain already that this is the path of least resistance for me. And it works great!
Could you elaborate on this?
Issue comment-triggered Actions have a write-access GITHUB_TOKEN, unless I’m mistaken. You could implement the /ok-to-test flow with that.
(I’m working on converting some of VSCode’s triage automation to Actions, for reference)