Skip to content
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

Merged
merged 13 commits into from
Jun 13, 2019
Merged

Set-up Continuous Deployment #513

merged 13 commits into from
Jun 13, 2019

Conversation

kernelwhisperer
Copy link
Contributor

@kernelwhisperer kernelwhisperer commented Jun 12, 2019

🦅 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

  • Include links to related issues/PRs
  • Update unit tests for this change
  • Update the relevant documentation
  • Clear dependencies on other modules that have to be released before merging this

@kernelwhisperer kernelwhisperer changed the title Release/v5.9.5 Set-up Continuous Deployment Jun 12, 2019
@kernelwhisperer kernelwhisperer marked this pull request as ready for review June 12, 2019 13:17
@kernelwhisperer kernelwhisperer requested a review from 0xGabi as a code owner June 12, 2019 13:17
@kernelwhisperer
Copy link
Contributor Author

Ready for review, feel free to merge as well @0xGabi

Copy link
Contributor

@0xGabi 0xGabi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks amazing! Thanks 🙌

@0xGabi 0xGabi merged commit 24431bc into master Jun 13, 2019
@0xGabi 0xGabi deleted the release/v5.9.5 branch June 13, 2019 18:37

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
Copy link
Contributor

@sohkai sohkai Jun 27, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document release steps
3 participants