Write RFC to use squash commits, research how GitHub stats work
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
From nf-core 2025 Core + Steering Retreat.
Assigned to: @edmundmiller
Deliverables:
- RFC document for squash commits adoption
- Research report on GitHub contribution statistics
- Analysis of impact on contributor stats
Context: Evaluate moving to squash commit strategy and understand implications for contributor attribution.
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 reviewing the squash-commit adoption question and GitHub contribution statistics relevant to contributor attribution. Done means producing the RFC, the GitHub statistics research report, and an impact analysis as listed in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100