Skip to content

Commit 374740c

Browse files
committed
doc: git-push: clarify "where to push"
Be clearer about what we're describing ("which repository" instead of "what to push"), and start with a positive "try X, then Y, then Z" instead of a negative ("if X is not specified.."). Signed-off-by: Julia Evans <[email protected]>
1 parent 0ec629d commit 374740c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Documentation/git-push.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,10 @@ DESCRIPTION
2222
Updates one or more branches, tags, or other references in a remote
2323
repository from your local repository.
2424

25-
When the command line does not specify where to push with the
26-
`<repository>` argument, `branch.*.remote` configuration for the
27-
current branch is consulted to determine where to push. If the
28-
configuration is missing, it defaults to 'origin'.
25+
To decide which repository to push to, Git uses the `<repository>`
26+
argument (for example `git push dev`), then if that's not specified the
27+
upstream configuration for the current branch, and then defaults
28+
to `origin`.
2929

3030
When the command line does not specify what to push with `<refspec>...`
3131
arguments or `--all`, `--mirror`, `--tags` options, the command finds

0 commit comments

Comments
 (0)