Skip to content
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

test: run on GitHub Actions #251

Draft
wants to merge 14 commits into
base: master
Choose a base branch
from
Draft

test: run on GitHub Actions #251

wants to merge 14 commits into from

Conversation

bendrucker
Copy link
Collaborator

Replaces Travis, whose OSS offering was killed by private equity, with GitHub Actions, so we actually have CI.

When calling `t.fail` with the whole `Error` object, all keys are printed. When the `err` has a `stream` property or similar this can be massively noisy to the point of overflowing GHA's default max log length for viewing in the browser.

While some error properties are useful (`stack`, `code`) this is the most straightforward way to cut the noise.
Comment on lines +13 to +19
- uses: actions/checkout@v3
- uses: dcodeIO/setup-node-nvm@v5
with:
node-version: iojs
- run: npm install
- run: npm test
env:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i ended up wrapping dcodeIO's action in ljharb/actions/node/install, which I use on 400 projects for node versions ranging from 0.4 to latest. I also have ljharb/actions/node/matrix to easily and dynamically create a matrix. You can also use ljharb/actions/.github/workflows/node.yml to encapsulate all of this in a single swoop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants