Support for a console GitReadonlyInterface?
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 355
- Forks
- 104
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 4
Description
We're currently facing a problem that arose from the differences between JGit and console git v2.11. Starting in 2.11, git uses a variable abbreviation length based on the number of objects in the repo. Our repo has now gotten sufficiently large that we're starting to see 10 character commit SHA abbreviations when calling git describe.
While I know this is primarily a JGit issue, these types of divergent behavior would be easily solved by just using the command-line git binary.
Would it be possible to extend support for the console git beyond the runner?
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 tracing the existing JGit integration and the runner's console-git handling, then compare the differing git describe behavior. The issue is done when console Git support is extended beyond the runner and the requested GitReadonlyInterface behavior is defined and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, scala
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100