-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: working off a release branch #40
Comments
Should be easy enough: https://docs.travis-ci.com/user/deployment/npm/ Though need to think about what the keys are going to be as it seems they have to be checked in 🤔 |
Thoughts on #41 ? |
Also it's an interesting approach to use the deploy trigger when there's a tag: https://docs.travis-ci.com/user/deployment/npm/#What-to-release (creating these on github would cause a deployment, for example) |
tag sounds like a legit trigger to me |
btw, https://github.com/sindresorhus/np with |
to summarise, here's the suggested release process:
|
I like it! Will look into it tomorrow. |
Problem: how do we make sure that the latest code in master resembles what's in npm?
The text was updated successfully, but these errors were encountered: