git-push: update documentation of git.push and git push --remote

* remove documented restriction of `git.push`

* add examples of providing multiple values.

* update `git.push` in config schema

* update CHANGELOG

Mention the new possible vaulues for `git.push` config
and ability to use `--remote` multiple times now,
including with string patterns.

Author: ysndr

CHANGELOG.md

@@ -33,6 +33,11 @@ to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   back to prompting the user if the heuristics are inconclusive. It can also run
   in non-interactive mode, which aborts if prompting would be needed.
 
+* `jj git push` now supports pushing to multiple remotes at the same time.
+  This can be configured via `git.push` set to a string pattern
+  or array of string patterns, or with the repeatable `--remote` flag,
+  which also accepts string patterns.
+
 ### Fixed bugs
 
 * The default pager flags now include `-K` (`--quit-on-intr`), so pressing

cli/src/config-schema.json

@@ -521,9 +521,19 @@
                     "default": "none()"
                 },
                 "push": {
-                    "type": "string",
-                    "description": "The remote to which commits are pushed",
-                    "default": "origin"
+                    "description": "The remote(s) to which commits are pushed",
+                    "default": "origin",
+                    "oneOf": [
+                        {
+                            "type": "string"
+                        },
+                        {
+                            "type": "array",
+                            "items": {
+                              "type": "string"
+                            }
+                        }
+                    ]
                 },
                 "record-synthetic-predecessors": {
                     "type": "boolean",

cli/tests/cli-reference@.md.snap

@@ -2,6 +2,7 @@
 source: cli/tests/test_generate_md_cli_help.rs
 description: "AUTO-GENERATED FILE, DO NOT EDIT. This cli reference is generated by a test as an `insta` snapshot. MkDocs includes this snapshot from docs/cli-reference.md."
 ---
+
 <!-- BEGIN MARKDOWN-->
 
 # Command-Line Help for `jj`
@@ -1847,9 +1848,13 @@ Before the command actually moves, creates, or deletes a remote bookmark, it mak
 
 ###### **Options:**
 
-* `--remote <REMOTE>` — The remote to push to (only named remotes are supported)
+* `--remote <REMOTE>` — The remote(s) to push to (can be repeated)
 
    This defaults to the `git.push` setting. If that is not configured, and if there are multiple remotes, the remote named "origin" will be used.
+
+   By default, the specified pattern matches remote names with glob syntax, e.g., `--remote '*'`. You can also use other [string pattern syntax].
+
+   [string pattern syntax]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns
 * `-b`, `--bookmark <BOOKMARK>` — Push only this bookmark, or bookmarks matching a pattern (can be repeated)
 
    If a bookmark isn't tracking anything yet, the remote bookmark will be tracked automatically.

docs/config.md

@@ -1819,12 +1819,10 @@ push to a different remote:
 
 ```sh
 jj config set --repo git.push "github"
+jj config set --repo git.push "regex:'^(remote|upstream)'"
+jj config set --repo git.push '["remote*", "upstream*"]'
 ```
 
-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.
-
 ### Default bookmarks and tags to fetch
 
 You can configure which bookmarks and tags to fetch by default per remote, using