Open GH Release
It seems like you could automate opening up a release on GitHub:
https://docs.github.com/en/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters
I wonder if git-cl would utilize a hook pattern like git-ps-rs is using now to allow this implementation.
The GH CLI may also be a good route to go: https://cli.github.com/manual/gh_release
Ultimately I would like a release flow, which I'm not sure all could be automated. For instance a release on a node project you need to remember to bump the version in package.json and run the npm install to update the lock version as well. Maybe a hook for this that could be project-based would work out well. Even fancier would be to detect if certain release flows applied to the project (like if it sees there's a package.json it knows to use the node release flow.) It would be nice too if it could be opinionated about whether release notes should be included in a tag or not -- they don't get gated until there's a tag, but then the catch 22 is that the release should ideally include the proper notes.
PS: this issue may be bloated and more of 2-3 semi-related issues in one.
Yeah, I think addressing an automated release flow is a much bigger topic than the current scope of git-cl.
That isn't to see that something like git-cl couldn't be the foundation for such a thing. But we would have to change the format of the change log entries such that we can indicate in git-cl the concept of breaking changes. With that and the existing categories of changes we would in theory be able to compute the next semantic version number. So something like it could very well be the foundation for something that facilitates and automates a release process.