-
Notifications
You must be signed in to change notification settings - Fork 79
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
Set-up Continuous Deployment #513
Conversation
- @aragon/[email protected] - [email protected]
Ready for review, feel free to merge as well @0xGabi |
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.
Looks amazing! Thanks 🙌
|
||
This hook runs after the build and testing steps have finished, and is purpose is twofold: | ||
|
||
1. Clean-up uncommitted changes resulted from installing or building, e.g.: lockfiles |
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.
Technically the git stash
probably isn't necessary, since npm uses the .gitignore
by default and it's unlikely travis will have changed any commits that could be tracked.
🦅 Pull Request
Closes #401
I think we might have a problem though: the tags on this branch will get removed when we squash and merge...Perhaps if we have only one commit is not an issue.
🚨 Test instructions
✔️ PR Todo