3 subject="""comment 2"""
4 date="2021-07-13T17:27:57Z"
6 Like Lukey said, your output does not show branches being "forcibly merged". What it shows
7 is `git fetch WD250G` running and fetching a
8 "WD250G/adjusted/master(hidemissing)" ref. That updates a previous version
9 of that it fetched from the remote before.
11 Nothing else will be done with that ref, as far as I can see. It's just
12 being maintained by git as a remote tracking branch, the same as it would
13 keep track of any other branch that happened to be on the remote.
15 You can configure git to not fetch this or other branches, by
16 changing the remote.WD250G.fetch git config.
18 Now, what `git annex sync` does do, when in an adjusted branch, is
19 propigate any changes that you have made to that branch back to the master
20 branch, and then it pushes the master branch over to the remote. And if the
21 remote is also in an adjusted branch, then running `git annex sync` on
22 the remote will merge in those changes from the master branch. But
23 when the branch is a --hide-missing branch, this process does not cause
24 files that are missing on the one repo to get deleted from the branch on