-
Notifications
You must be signed in to change notification settings - Fork 74
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
not working for files in an auxiliary worktree (using git-worktree) #86
Comments
How to do that?
If |
Closing . If the above |
Ok thanks for the information - I believe that the problem has something to do with git-link not being able to determine what the upstream repository and tracked branch is in the case when a "git-worktree" branch is being used. If I have more time to investigate, and find out anything more specific, I'll reopen. |
FWIW, I routinely use |
Given a git repository contained in the folder
foo
, if (from this folder) the commandgit worktree add ../foo-worktree-otherbranch otherbranch
is executed, a worktree will be created for theotherbranch
branch in the folder../foo-worktree-otherbranch
(relative to thefoo
folder).When editing a file within the
foo-worktree-otherbranch
folder, and attempting to usegit-link
, the errorRemote 'origin' not found
occurs. Instead,git-link
should be able to correctly identify the remote and branch. In the particular case this was tested under, thefoo
repository didn't even have anorigin
remote (but did have other remotes).The text was updated successfully, but these errors were encountered: