You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing failure to delete a branch in a VS Code terminal, when this extension is enabled. So: doing git work in an integrated terminal, through means other than VS Code + this extension.
The failure is due to the branch not existing. But this nonexistence is due to the fact that the request to delete branch foo is somehow getting garbled into foo.github-pr-owner-number just from the mere fact that this extension is enabled.
You're seeing some output from R, in which we're using the gert R package, which ultimately is using libgit2:
✔ Deleting local "switch-r-pkg-testing-shortcut" branch.
Error in libgit2::git_branch_delete :
could not find key 'branch.switch-r-pkg-testing-shortcut.github-pr-owner-number' to delete
Note this suffix, which is not actually part of the branch name and would seem to somehow come from this extension:
It feels like the extension is somehow inserting itself here, under the assumption that it "owns" all of the git(hub) work, or at least any related to managing PR-associated branches.
The text was updated successfully, but these errors were encountered:
I'm seeing failure to delete a branch in a VS Code terminal, when this extension is enabled. So: doing git work in an integrated terminal, through means other than VS Code + this extension.
The failure is due to the branch not existing. But this nonexistence is due to the fact that the request to delete branch
foo
is somehow getting garbled intofoo.github-pr-owner-number
just from the mere fact that this extension is enabled.You're seeing some output from R, in which we're using the gert R package, which ultimately is using libgit2:
Note this suffix, which is not actually part of the branch name and would seem to somehow come from this extension:
It feels like the extension is somehow inserting itself here, under the assumption that it "owns" all of the git(hub) work, or at least any related to managing PR-associated branches.
The text was updated successfully, but these errors were encountered: