config-merge without @remote ?

[yched]

Wow, the pages and diagrams describing the different flows are awesome, and should greatly help developpers figure out the challenges of config workflow.

Just some feedback on that awesome work :

• Nitpick : IMO it could help the reader be sure he follows along if the text referred to the diagram labels (a, b, ..., 1, 2, ..., F1, F2, ...) all the way through the end. AFAICT, It's the case at the beginning of the "git flow" text, and less towards the end ?
• The part I'm a bit confused and intrigued about is the case of config-merge without a @Remote arg, which is mentioned in the "git workflow" page, but could deserve more details IMO :-) - maybe on its own page ? since that use seems orthogonal to the question of "git or rsync model" (which itself boils down to "can the remote push to git", right ?)

As discussed in the comments on https://pantheon.io/blog/configuration-workflow-drupal-8-sites, I understand "config-merge @Remote" to help with the case where config changes can be made on site instances (like stage or prod) that otherwise typically don't commit back to git.

But it's less clear to me what "config-merge from a branch rather than from a @Remote" does, compared to a vanilla "git merge all the code and config yamls from that branch over to mine" ?