threads / discuss / 55182

Wrong configuration variable mentioned in git-push documentation (examples section)

Subject: Wrong configuration variable mentioned in git-push documentation (examples section)

## tl;dr

2 messages between Feb 22, 2021 and Feb 25, 2021.

replies: 1people: 2as markdown or json

Adam Sharafeddine· Feb 22, 2021, 05:07 UTC · lore
Hello

In the file Documentation/git-push.txt under the EXAMPLES section, specifically under `git push origin`::, remote.origin.merge configuration variable is said to configure the upstream branch for the origin remote, when in fact it should be branch.<name>.merge, where <name> is the name of the local branch at which HEAD is currently pointing to.

Here's en excerpt:
Show 5 quoted lines
> `git push origin`::
>         Without additional configuration, pushes the current branch to
>         the configured upstream (`remote.origin.merge` configuration
>         variable) if it has the same name as the current branch, and
>         errors out without pushing otherwise.

I'm still learning Git so I thought I would share this with you (I got confused reading the examples). Maybe I'll learn something new or/and correct the aforementioned error.

Regards

-- Adam

Philippe Blain· Feb 25, 2021, 13:57 UTC · re: Adam Sharafeddine · lore

Re: Wrong configuration variable mentioned in git-push documentation (examples section)

Hi Adam,
Le 2021-02-22 à 00:07, Adam Sharafeddine a écrit :
Show 25 quoted lines
> Hello
> 
> In the file Documentation/git-push.txt under the EXAMPLES section,
> specifically under
> `git push origin`::, remote.origin.merge configuration variable is
> said to configure the
> upstream branch for the origin remote, when in fact it should be
> branch.<name>.merge,
> where <name> is the name of the local branch at which HEAD is
> currently pointing to.
> 
> Here's en excerpt:
> 
>> `git push origin`::
>>          Without additional configuration, pushes the current branch to
>>          the configured upstream (`remote.origin.merge` configuration
>>          variable) if it has the same name as the current branch, and
>>          errors out without pushing otherwise.
> 
> 
> I'm still learning Git so I thought I would share this with you (I got
> confused reading
> the examples). Maybe I'll learn something new or/and correct the
> aforementioned error.
> 

You are completely right, that example seems to use an old and now non-existent (at least, undocumented in git-config(1) [1]) configuration variable. I encourage you to fix it yourself and submit a patch :) See [2] for a nice tutorial on how to do this if you are interested.

Cheers, Philippe.

[1] https://git-scm.com/docs/git-config [2] https://git-scm.com/docs/MyFirstContribution

← back to recent threads