You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current way of cutting release is very manual (at least in 0.1.1, see README)
Setup a GitHub Workflow, Travis CI build, .... to automate this as much as possible and reduce errors.
Goal
This issue aims to cover the 1st automation step:
bump the version in the npm package.json file + tag the related commit
The current way of cutting release is very manual (at least in 0.1.1, see README)
Setup a GitHub Workflow, Travis CI build, .... to automate this as much as possible and reduce errors.
Goal
This issue aims to cover the 1st automation step:
A note about GitHub Actions/Workflows
[UPDATE 2020-07-07] it is now possible to manually triggered a GH Workflow via the new
workflow_dispatch
event type, see https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/Triggering manual jobs/builds is currently not available
The workaround suggested in the community forum is to use a
repository dispatch event
with a custom event typeAlternatives to
repository dispatch event
We could trigger the job on
GitHub Token
In addition, we may have to use a custom github token if the default action one has not enough permissions, see https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token
Master Branch Protection
As the master branch currently does not accept push without creating Pull Request, we may
administrator
privilege to ensure thebranch-protection-bot
action workRelease resources
Alternatives
https://semantic-release.gitbook.io/semantic-release/
The text was updated successfully, but these errors were encountered: