gradle / gradle/develocity-build-validation-scripts
Configured Git options are respected when checking out a specific commit id in gradle-exp5 and maven-exp4
Open
user-facing
- Dominant language
- Shell
- Stars
- 115
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
Always `clone` instead of `fetch` when Git options are different from the default (--depth=1).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the checkout logic in the gradle-exp5 and maven-exp4 scripts, focusing on how configured Git options are compared with the default --depth=1 behavior. Verify the scripts use clone rather than fetch when options differ, while preserving the existing behavior for default options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100