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
Since I was add as collaborator, I'd propose some changes to improve this library quality.
In a couple days I'll create more proposals and pull requests but this one is about automating the deployment process.
Proposal
My idea here is to use semantic-release to do this process for us.
For those who doesn't know what's this about, semantic release takes care of our versioning using Angular commit message versioning:
It means each commit made needs to follow this structure because it'll be used to:
decide what version would be next. If a commit with fix prefix is merged into master, then semantic release will automatically bump from 2.2.1 to 2.2.2 (minor version) for example;
Auto generates Change log when it happens;
Auto generates tag publish;
Needs
To set this flow only the only thing I need is a NPM_TOKEN environment variable to publish to npm and a GH_TOKEN to publish change logs and tags:
The rest is on me :)
The text was updated successfully, but these errors were encountered:
Hi everyone.
Since I was add as collaborator, I'd propose some changes to improve this library quality.
In a couple days I'll create more proposals and pull requests but this one is about automating the deployment process.
Proposal
My idea here is to use semantic-release to do this process for us.
For those who doesn't know what's this about, semantic release takes care of our versioning using Angular commit message versioning:

It means each commit made needs to follow this structure because it'll be used to:
fix
prefix is merged into master, then semantic release will automatically bump from2.2.1
to2.2.2
(minor version) for example;Needs
To set this flow only the only thing I need is a
NPM_TOKEN
environment variable to publish to npm and aGH_TOKEN
to publish change logs and tags:The rest is on me :)
The text was updated successfully, but these errors were encountered: