nelsonic / nelsonic/github-scraper
Should we scrape/extract the list of commits for a repo?
Open
Nobody has claimed this yet.
enhancement
help wanted
question
- Dominant language
- JavaScript
- Stars
- 456
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
I hypothesize that crawling the list of commits e.g:
will be interesting to see/track:
- who makes the most commits to the project
- when (_what time_ of day/night) people do their work
- what did the person contribute? (docs, code improvement, tests, typo, deps update?)
@iteles we don't have this on our "road-map" right now. #discuss
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
No file, test, or entry point is named in the issue. Start by reviewing the repository context and discussion, then define the commit data and analyses required before identifying implementation work; done would mean an agreed scope or a concrete follow-up issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100