nodejs / nodejs/node-core-utils
git-node: `git node bisect`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
https://twitter.com/targos89/status/982158028878196736
Outline:
git node bisect --from 20180101 [--to 201810406] /path/to/test.js- Detect the right arch, then download correct binaries from https://nodejs.org/download/nightly/ , decompress it, run the test with
bin/node, bisect until it finds two consecutive nightlies where the exit code of the test becomes different- Let the user configure where the files are downloaded via
ncu-config set tmpdir, default can be.ncu/tmpor/tmp
- Let the user configure where the files are downloaded via
- Grab the sha from the nightlies, suggest the user to run:
git bisect start <nightly1-sha> <nightly2-sha> --git bisect run "make -j8 && ./node /path/to/test.js"
Contributor guide
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 by examining the existing node-core-utils CLI entry points and configuration handling for ncu-config set tmpdir; the issue names no specific files or tests. Review the Node.js nightly download layout and the proposed git bisect commands. Done means a git node bisect workflow can select the architecture, download and run nightlies, identify the exit-code change, and suggest the matching Git commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, node.js
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100