Support SHA256 git object format
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 12k
- Forks
- 332
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 17
Description
Summary 💡
When trying to run Onefetch inside a git repo which uses the SHA256 object format, instead of the default SHA1, it immediately errors out:
Error: Failed to load the git configuration
Caused by:
The key "extensions.objectFormat=sha256" was invalid
Motivation 🔦
While the SHA256 object format is not yet used by default, it will eventually be set as the default by upstream git.
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 reproducing the failure in a Git repository using the SHA256 object format, then trace Onefetch's Git configuration loading from the reported invalid extensions.objectFormat key. Done means Onefetch runs successfully in that repository instead of rejecting the configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100