chore(build): activate GitHub workflow for PRs #427
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's included
Notes
Why?
Running unit tests in Travis seems to be getting increasingly slower with each new test. This is an attempt to remove Pull Requests from Travis and move those confirmations into GitHub.
We will still be using the same Travis scripts to compile the GUI, and push to the
curiosity-frontend-build
repo, which in turn pushes to the Platform environments. This includes the exact same scripts as the GitHub workflow... Travis is just slowerHow to test
Once this is merged
Example
...
Updates issue/story
Ongoing and #275
PRs - #436 #435 #434