Add GitHub Actions workflow for testing React components #360
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
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 adds a GitHub Actions workflow YAML file for running the Jest test suite added in #359.
This new workflow is set to run on any pull request that changes files within
packages/react-components, regardless of the branch being targeted by the PR. This is to allow us the freedom to have longer-running feature branches for particular components that we repeatedly do PRs against before merging the entire feature branch back intomain. Ex: A pull request fromfeature/card-vertical-image-handlinginto a longer-runningfeature/cardbranch.For now, I've left out any step that uploads the Jest log anywhere. Some workflows do this using actions/upload-artifact, but I think we can probably get by without it by using the temporary logs in the workflow run.
In 60cda50 I'm attempting to use the version of Node.js specified in our
.nvmrcfile rather than hard-coding it. I've confirmed thatnvm usestill works for me locally without thevin the version number.