nodejs / nodejs/node-core-utils
command to know in which release branch(es) a specific commit is
Open
Nobody has claimed this yet.
feature request
- Dominant language
- JavaScript
- Stars
- 313
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
I don't think we have a simple automated way to do that now. Due to the way we land commits in releases, we cannot just search for the commit SHA in release branches.
I think it would be useful to have a command for that.
Prior art in V8: https://github.com/v8/v8/blob/master/tools/release/mergeinfo.py
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 reading the V8 prior art in tools/release/mergeinfo.py and surveying the existing node-core-utils CLI entry points. The command should report which release branches contain a specified commit despite the project's release-landing workflow; verify it against representative commits and release branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli, release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100