docs: fix some automerge fallout

I enabled automerge for #2994, but forgot to actually *push* my changes before resolving all the conversations, so GitHub insta-merged it. This just addresses Ilya and Philip's final comments on #2994. Signed-off-by: Austin Seipp <[email protected]>
jj-vcs · Feb 9, 2024 · c8f703f · c8f703f
1 parent 015c52b
commit c8f703f
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/docs/config.md b/docs/config.md
@@ -525,18 +525,22 @@ To change this behavior, you can modify the [repository
 configuration](#config-files-and-toml) variable `git.fetch`, which can be a
 single remote, or a list of remotes to fetch from multiple places:
 
-```
+```sh
 jj config set --repo git.fetch "upstream"
 jj config set --repo git.fetch '["origin", "upstream"]'
 ```
 
 Similarly, you can also set the variable `git.push` to cause `jj git push` to
 push to a different remote:
 
-```
+```sh
 jj config set --repo git.push "github"
 ```
 
+Note that unlike `git.fetch`, `git.push` can currently only be a single remote.
+This is not a hard limitation, and could be changed in the future if there is
+demand.
+
 ### Automatic local branch creation
 
 When `jj` imports a new remote-tracking branch from Git, it can also create a