mafintosh / mafintosh/node-core-commit-stream
Make it generic?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Could this tool not be used against any public repo if pathname was part of the opts obj?
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
The issue only identifies the tool's opts object and a pathname option; start by inspecting the repository entry point and how it currently accesses Node.js core commit data. Define what public-repository support should accept and return, then verify the stream still produces structured commits in newest-to-oldest order for a non-core repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100