Add --check option, for CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
GitHub recommends ncc for building actions for GitHub Actions. When making a change to the repository for an existing action, it's very easy to forget to re-run ncc, so that the generated code is updated.
I would like to build an action that can verify that the code in the repository matches the generated code from ncc. To do that, it would be convenient to have a ncc --check option, which would compile the code in the repo, compare the result to the generated file that already exists, and exit with status code 0 if they match, or status code 1 if they do not match. This could be turned into an action to run on repositories for other actions, to make sure that code changes include regenerating the code.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ncc command-line entry point and inspect how compilation writes the generated bundle. Compare the generated output with the repository's existing file and verify the requested exit statuses; the issue names no specific file or test, so those must be located in the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100