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.
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
Switch from Travis CI to GitHub Actions #504
Switch from Travis CI to GitHub Actions #504
Changes from 4 commits
050b59e
eb961c1
efde3b6
2d81a5c
1e094d0
7487064
c7ffbd3
394da1a
6751832
91dd5b5
b9a65f6
13f5e60
e1fdcb5
87e7375
f8ceedc
ef390cf
108eb6e
d9961a1
0a2c180
67f38e9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
fail-fast: false is needed here
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.
On my experience, this not right, seem need another job wait for matrix, not sure. I tried in this way before.
So I dont use parallel https://github.com/fisker/id-placeholder/blob/ae506a0069bb459f6100f2c317f377ba9f8651de/.github/workflows/continuous-integration.yml#L52
Also, this action some times fail for no reason, issue can found on their repo, so I use continue-on-error
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.
The
parallel-finished
is what they document should be used when running multiple tests in parallel: https://github.com/coverallsapp/github-action#inputsI added the
continue-on-error
on error now 👍 Good feedback!This file was deleted.
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.
XO is now run twice, both on
test
andlint
.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.
@sindresorhus Yes and no. In the GitHub CI pipe
test-coverage
is run rather thantest
. Partly to get coverage report and partly to move thexo
part from being run on every Node.js version to being run just once as part of the linting flow.So,
test.yml
runstest-coverage
whileother.yml
(suggestion on better name?) runslint
andintegration
I thought it was best to leave the
test
as is, as that's likely the one that gets run manually the most.