Fix issue where "git subrepo commit" incorrectly gives error "There is no worktree available".#635
Open
reidgould wants to merge 1 commit intoingydotnet:masterfrom
Open
Fix issue where "git subrepo commit" incorrectly gives error "There is no worktree available".#635reidgould wants to merge 1 commit intoingydotnet:masterfrom
reidgould wants to merge 1 commit intoingydotnet:masterfrom
Conversation
…s no worktree available".
Gems
approved these changes
Mar 30, 2026
Gems
left a comment
There was a problem hiding this comment.
Thank you very much for the PR! I applied the patch to my local subrepo installation and it fixed the problem 👍🏻
Collaborator
|
Good catch, but it appears this is an incomplete solution. In addition to the change in command-setup() it appears the same issue is in subrepo:status and in error-join() after section 6. It would also be great if a test could be added. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix issue where
git subrepo commitincorrectly gives error "There is no worktree available".I encountered a merge conflict in a subrepo that has a name starting with a period character,
.obsidian.I follow all the recommended steps, resolving the conflicts and committing them.
But on the last step, the following error occurs.
I found that the
git subrepo commitcommand uses the rawsubdirvariable to find the worktree, instead of the encodedgitrefvariable.This PR changes
committo use the correct variable.