oxidecomputer / oxidecomputer/buildomat
want git clone depth control
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/oxidecomputer/cockroach has 70,000 commits and it takes forever to clone. --depth 1 would be sufficient for my use case (although I'd need to find a workaround for it wanting to use git describe as part of the version string).
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
Start by locating where buildomat clones repositories and where it invokes git describe for the version string. Confirm how clone depth is configured, then verify that a depth-1 clone works without breaking version generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100