From: Julia Evans via GitGitGadget Date: Tue, 30 Sep 2025 19:58:32 GMT Subject: [PATCH v4 3/5] doc: git-push: clarify "where to push" Message-ID: <244c35ef2bdcd211800798bc694b194c8feea1bd.1759262314.git.gitgitgadget@gmail.com> In-Reply-To: From: Julia Evans It's not obvious that "`branch.*.remote` configuration"` refers to the upstream, so say "upstream" instead. The sentence is also quite hard to parse right now, use "defaults to" to simplify it. Signed-off-by: Julia Evans --- Documentation/git-push.adoc | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/Documentation/git-push.adoc b/Documentation/git-push.adoc index 25d972f248..acdf25e5cd 100644 --- a/Documentation/git-push.adoc +++ b/Documentation/git-push.adoc @@ -23,10 +23,8 @@ Updates one or more branches, tags, or other references in a remote repository from your local repository, and sends all necessary data that isn't already on the remote. -When the command line does not specify where to push with the -`` argument, `branch.*.remote` configuration for the -current branch is consulted to determine where to push. If the -configuration is missing, it defaults to 'origin'. +The `` argument defaults to the upstream for the current branch, +or `origin` if there's no configured upstream. When the command line does not specify what to push with `...` arguments or `--all`, `--mirror`, `--tags` options, the command finds -- gitgitgadget