Set up CI in GitHub Actions #955
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chriskrycho
approved these changes
Nov 20, 2019
Comment on lines
+15
to
+17
| # early issue detection: run CI weekly on Sundays | ||
| schedule: | ||
| - cron: '0 6 * * 0' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a definition for a "CI" GitHub workflow that aims to give equivalent coverage to that of our current Azure Pipelines setup.
Once we're happy with the setup, and assuming a quorum of the Typed Ember folks are on board, we can remove the Azure config files and update our Required Checks for PRs.
One note: I played some with
actions/cacheto persist dependencies across builds and speed things up a bit, but I'm not sure it's quite baked enough for our needs yet. It should be easy enough to layer on in the future if we figure out a way to use it effectively.