-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(request) Use local repos for fetch instead of cloning #44
Comments
proof of the concept implementation available @ https://github.com/mgurov/Gitifier/tree/noClonesButInlineFetchingForLocal |
Bump. This is a huge pain as I work on several large repos. Any issue with the cons listed above? |
Point 1 is what I'm worried about every time someone asks about this - |
From my personal experience, neither of the points appeared to be a problem.
before fetch: ~/tmp/git/clone$ git lol
* c1f134c (HEAD, origin/master, origin/HEAD, master) initial Gitifier fetches new revisions: ~/tmp/git/clone$ git fetch
remote: Counting objects: 5, done.
remote: Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
From /Users/mgu/tmp/git/repo
c1f134c..a582210 master -> origin/master as we see, local references hasn't been changed ~/tmp/git/clone$ git lol
* a582210 (origin/master, origin/HEAD) change
* c1f134c (HEAD, master) initial we do pull and still see the same change ~/tmp/git/clone$ git pull
Updating c1f134c..a582210
Fast-forward
a | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
~/tmp/git/clone$ git lol
* a582210 (HEAD, origin/master, origin/HEAD, master) change
* c1f134c initial Conclusion.The feature is useful and adds new value to the Gitifier. The only potentially negative, from the user experience point of view, effect of some commits missed by Gitifer on manual fetch is negligible for many workflows, where Gitifier is not the main git tool. This issue can be mitigated by preserving the original option of cloning remote repository into Gitifier's own copy. This option could also be useful to watch repositories user does not actively involved in (and has no working directory checked out). |
+1 |
+1 |
I really want this for tracking repos I already have on the system. This would be handy. |
In case I already have a repository cloned on my workstation for active work with it, it could be beneficial to use it for fetches instead of cloning a new one. Especially if the repo is voluminous. That would bring following advantages:
potential issues:
The text was updated successfully, but these errors were encountered: