It doesn't show shallow repo's commits
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
After clone with --depth n and open with Gittyup, there is no git commit log at all.
The gitk or other tools can show the shallow repo correctly.
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 reproducing the issue with a repository created using git clone --depth n, then compare Gittyup's empty commit log with the same shallow repository in gitk. Done means Gittyup displays the shallow repository's available commits after opening it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100