Skip to content
Discussion options

You must be logged in to vote

Unlocking the primary checkout is necessary but not sufficient.

A linked worktree has its own GIT_DIR under .git/worktrees/.... During git worktree add, Git runs the git-crypt smudge filter in that context. If the filter is configured as plain git-crypt smudge, git-crypt looks for the key in the linked-worktree metadata rather than the repository’s shared Git directory, and checkout fails before T3 Code can start the thread.

After unlocking the repository, run the following once from its primary checkout. It stores the commands in the clone-local Git configuration, so every linked worktree resolves the shared common directory:

git config --local filter.git-crypt.smudge \
  'GIT_DIR="$(git…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by bjesuiter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant