release-please-action
release-please-action copied to clipboard
automated releases based on conventional commits
It shouldn't be too hard to add some unit tests for our logic.
Currently it can be really long and hard to read. ```yml changelog-types: '[{"type":"feat","section":"Features","hidden":false},{"type":"fix","section":"Bug Fixes","hidden":false},{"type":"gyp","section":"Miscellaneous","hidden":false}]' ``` Maybe something like: ```yml changelog-types: - '{type: }' - '{type: }' ```
Motivation: It would enforce type coming from release-please package. Artifacts: * https://github.com/actions/typescript-action (Possible inspiration)
I really enjoy using release-please (thanks for this project). I introduce to my electron project, which need artifact on release My previous release like this, include binary for auto-updates. ...
Same from https://github.com/gengjiawen/node-gyp/pull/2/files. The history changelog is very important. Maybe just prepend new in file header.
I really like this tool. Maybe an official badge so we can add it to `README.md` to make it more known.
It would be nice to know the version information to use in a workflow when a release is NOT created. For instance, building release candidate artifacts (v1.1.1-rc1) to push to...
We're using this action and its output to trigger a publish workflow in the same job if a new release PR has just been merged, similar to this example: https://github.com/google-github-actions/release-please-action#automating-publication-to-npm...
After successfully releasing `5.0.0-beta.1`, release-please-action creates PR with with same version `5.0.0-beta.1` instead `5.0.0-beta.2` or just `5.0.0`. #### Environment details - OS: windows-latest - Node.js version: 4.16.0 - npm version:...