ci: use release-please #280
Conversation
|
@sebhoerl more details about what I say here
I think it can be useful, seeing that the default commit title and body are defined as
In my day to day uses, I always remove the list of commits that compose the merged branch, because they can be internal fixes of the branch, etc. And I fear that with the automatic changelog generation will include this body, and then make things a little messy. But this is only Quality-Of-Life for people that merge the branches, and maybe you want to keep all options available. Up to you to decide if its relevant or not. |
PR contents
Release Please
Presentation and usage
Release Please will create and update a release PR when the develop branch receives pushes. When we are ready to release, simply merge the PR.
Commits on the develop branch have to follow the conventional commit convention. This can be done by squash-merging the PRs (highly recommended) and having the title in conventional commit style (hence the action that checks the PRs' titles). We can force the squash-merging and also modify the commit message in the settings, see here. Commits on the working branch don't have to be conventional commits.
Release Please config
See here for the config options of Release Please.
release-type:simple(a repository with a version.txt and a CHANGELOG.md)versioning strategy:
default(breaking changes bump the major version, features bump the minor version, bugfixes bump the patch version)TODO
Closes #276
Closes #188