Stabilize SHA-256 support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
In git2@0.21.0 we have added SHA-256 support behind an unstable Cargo feature unstable-sha256.
It is done this way because the upstream libgit2 v1.9 also marks it as experimental. The plan in upstream is that there will be a stable SHA-256 support (+ reftable I believe) in libgit2 v2, and it is coming: https://github.com/libgit2/libgit2/discussions/7149#discussioncomment-16765611. We should move it out from unstable when upstream is ready.
cc rust-lang/git2-rs#1090
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 with the unstable-sha256 feature declaration in Cargo.toml and review the linked upstream libgit2 discussion for the stable-support criteria. Confirm the upstream release is ready, then determine the repository changes needed to remove the unstable gating; done means SHA-256 support is exposed through the stable configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100