-
Notifications
You must be signed in to change notification settings - Fork 2
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
Revise deploy steps #105
Revise deploy steps #105
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Say goodbye to deploy.sh XDDD
.travis.yml
Outdated
@@ -15,6 +15,8 @@ install: | |||
before_script: | |||
- yarn flow | |||
- yarn lint | |||
|
|||
script: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If test break on script
, will it continue the rest processes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to this doc, I believe it's “yes”.
Or I was thinking to move coverall
to after_success
so it only runs after tests passed?
20338ce
to
5d9ba64
Compare
Rebased with latest |
Summary
This PR tries to use native deploy stage on Travis CI by using its script provider.
Releasing a new version now require you to run
yarn bumpversion
locally before submitting a release PR. It will update allpackage.json
underpackages/
, commit those changes and tag it with a version tag.Travis CI will run
yarn release
on master to only publish packages to npm.