Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
offer shallow clone option
See original GitHub issueAs a user who often contributes translations, documentation improvements, etc. I rarely have much use for an offline copy of a repo’s entire history. I would trade that for an option to clone shallowly, so that my workflow can be faster.
So, how about something like [ ] fetch only the repo's current state that executes git clone --depth=1 --no-single-branch ...? Maybe not 1, but ... only recent history or some small portion of it. I’m curios about how that could be determined before cloning.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello! 👋
We talked about this feature and we’re gonna explore our options during the next weeks 😄
I could be a super easy thing to do… but we want to make sure there are no side-effects when the app is using a shallow clone, so we’ll need to investigate a bit 🕵️♂️
Stay tuned!
Hi @sergiou87 and @tidy-dev! Is there any chance that you could look into this issue? It would be awesome to have the option for a shallow clone in GitHub Desktop, especially if you are limited in bandwidth or storage.