Consider adding a "shortest hash abbreviation" as a data point
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 12k
- Forks
- 332
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 17
Description
Summary 💡
See https://blog.cuviper.com/2013/11/10/how-short-can-git-abbreviate/.
This can be handy for people working on the repo in question. It's also just a cool statistic.
Motivation 🔦
No response
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
No file, test, or entry point is named in the issue. Start by reading the linked Git abbreviation article and locating onefetch’s existing data-point collection and output path; done means the CLI reports the shortest hash abbreviation as an additional statistic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100