-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update workflows #63
base: master
Are you sure you want to change the base?
Update workflows #63
Conversation
- name: Yarn Test | ||
run: yarn test --watchAll=false |
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.
Filed #64 because we don't have any react tests for this new workflow to run
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.
:oof:
steps: | ||
- uses: actions/checkout@v1 | ||
- name: Install Dependencies | ||
run: yarn |
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.
We're using npm
. Will using yarn
in our actions cause problems?
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.
Honestly, I have no idea. It seems to work, but 🤷 . We should probably hold off on this until we actually have unit tests in js too
What broke / What you're adding
Now that our React app is gonna be used more and more, I figured it's time to update our github workflows to reflect that.
How you did it
How to test it and how to try to break it
Notice that the golang nor react workflows don't run on this PR but the docker build image still doe