Skip to content

Move scratch-parser to GitHub Actions#67

Merged
delasare merged 4 commits into
masterfrom
rd/ENG-41/move-to-gha
Oct 18, 2023
Merged

Move scratch-parser to GitHub Actions#67
delasare merged 4 commits into
masterfrom
rd/ENG-41/move-to-gha

Conversation

@delasare

@delasare delasare commented Oct 10, 2023

Copy link
Copy Markdown
Contributor

Resolves

https://scratchfoundation.atlassian.net/browse/ENG-41

  • Adds CODEOWNERS file
  • Adds .nvmrc file
  • Includes package-lock
  • Adds GHA workflow
  • Removes CirclCI files

Ron de las Alas added 4 commits October 10, 2023 10:13
chore: bump node v

chore: include the package-lock

chore: split the lint and test commands
@delasare
delasare force-pushed the rd/ENG-41/move-to-gha branch from ca19152 to 213f4fe Compare October 10, 2023 18:31
@delasare delasare changed the title Rd/eng 41/move to gha Move scratch-parser to GitHub Actions Oct 11, 2023
@delasare
delasare marked this pull request as ready for review October 11, 2023 15:37

@cwillisf cwillisf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks great overall! One question / potential change...

Comment thread .gitignore
Comment thread package.json
"test:coverage": "tap test/{unit,integration}/*.js --coverage --coverage-report=lcov",
"test:benchmark": "node test/benchmark/performance.js",
"test": "npm run test:lint && npm run test:unit && npm run test:integration",
"test": "npm run test:unit && npm run test:integration",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why separate test:lint from test? Seems like undoing this change and removing the separate npm run test:lint step in the workflow would work...?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I always think of linting and testing as two different things, so my preference is to separate those two scripts. I like the separation in the workflow so that I can tell what event had issues. I would even go as far as saying unit and integration tests are two different things. :)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Heh - fair enough. I definitely agree that including linting in npm test is annoying when you're working on the tests!

@delasare
delasare requested a review from cwillisf October 12, 2023 14:56
@delasare
delasare merged commit 8aa5288 into master Oct 18, 2023
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 5.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants