I employ Git worktrees, that's a standard feature for working with multiple working trees. Among other properties, all Git worktrees (created from a single repo clone) share:
repo clone
local branches
remotes
git config
stashes
Basically, everything that is locally done to a clone in one of working tree is automatically "becomes available" in another working trees. For example, I can e.g. stash something in one working tree and pop the stash in another.
Fork works really good with this configuration/does not mess up anything - everything is fine (as it should, because, as far as I understand, working trees are meant to be compatible with any Git client and etc).
The "problem"/"challenge"
Even though Fork does work fine with everything above, when I pin a branch while working with Fork in one working tree, this “attribute” remains local only to that working tree.
Expectation
I do expect that "pinned" branches would be shared between the working trees, i.e. would be (logically) attribute of a repo (or git configuration of a repo), rather than of a particular working tree.
Thoughts
I don't know how pinning is implemented currently, but I guess that if it was implemented through (or similarly) (repo scoped) git config, that could help with sharing these changes between the working trees, the same way as any other repo-specific properties.
A bit of context
I employ Git worktrees, that's a standard feature for working with multiple working trees. Among other properties, all Git worktrees (created from a single repo clone) share:
Basically, everything that is locally done to a clone in one of working tree is automatically "becomes available" in another working trees. For example, I can e.g. stash something in one working tree and pop the stash in another.
Fork works really good with this configuration/does not mess up anything - everything is fine (as it should, because, as far as I understand, working trees are meant to be compatible with any Git client and etc).
The "problem"/"challenge"
Even though Fork does work fine with everything above, when I pin a branch while working with Fork in one working tree, this “attribute” remains local only to that working tree.
Expectation
I do expect that "pinned" branches would be shared between the working trees, i.e. would be (logically) attribute of a repo (or git configuration of a repo), rather than of a particular working tree.
Thoughts
I don't know how pinning is implemented currently, but I guess that if it was implemented through (or similarly) (repo scoped) git config, that could help with sharing these changes between the working trees, the same way as any other repo-specific properties.