-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
git worktrees don't work #83
Labels
bug
Something isn't working
Comments
lnc3l0t
added a commit
to lnc3l0t/gitlinker.nvim
that referenced
this issue
May 19, 2023
A new option has been added to config: bare_repos. It is a list of pairs { git_dir, git_work_tree }. If the plugin is used in a buffer which belongs to a bare repository, after the first call to git (`git rev-parse`) which returns error since buffer is not in a git repo, subsequent similar calls will be made with the `--git-dir` and `--git-work-tree` flags. After the buffer has been found to be in one of the bare repositories the user added to the config the information is cached for subsequent calls in the session
lnc3l0t
added a commit
to lnc3l0t/gitlinker.nvim
that referenced
this issue
May 19, 2023
A new option has been added to config: bare_repos. It is a list of pairs { git_dir, git_work_tree }. If the plugin is used in a buffer which belongs to a bare repository, after the first call to git (`git rev-parse`) which returns error since buffer is not in a git repo, subsequent similar calls will be made with the `--git-dir` and `--work-tree` flags. After the buffer has been found to be in one of the bare repositories the user added to the config the information is cached for subsequent calls in the session
stevanmilic
pushed a commit
to stevanmilic/gitlinker.nvim
that referenced
this issue
Nov 12, 2023
hi @kekscode , let's track this issue here: linrongbin16/gitlinker.nvim#107 |
Is this being worked on? |
hi @msharran, let's track it here: linrongbin16/gitlinker.nvim#107 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is:
--bare
and addedmain
branch asgit worktree add
Failed to get closest revision in that exists in remote 'origin'
errorTo Reproduce
...just the default config with no changes to mappings, callbacks or anything else is fine.
git clone --bare https://github.com/ruifm/gitlinker.nvim && cd gitlinker.nvim.git && git worktree add main
main
and open a file there, e.g.README.md
<leader>gy
(default mapping). The errorFailed to get closest revision in that exists in remote 'origin'
should appear.Expected behavior
Open
README.md
formain
branch of 'ruifm/gitlinker.nvim' on GitHub.System (please complete the following information):
The text was updated successfully, but these errors were encountered: