Re: please add link / url to remote - when - git push

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 30, 2023, 06:55 UTC
Message-ID: <xmqqa5s0egzn.fsf@gitster.g>
In-Reply-To: <20231030063633.GA7451@tb-raspi4>

Torsten Bögershausen <tboegi@web.de> writes:

Show 33 quoted lines

> On Sun, Oct 29, 2023 at 06:15:35PM -0500, Alexander Mills wrote:
>> When a feature branch is pushed, we get a link in the console to go to
>> remote, however when I push directly to main/master, no such link, eg:
>>
>> ```
>> alex.mills@alex node-be % git push
>> Enumerating objects: 20, done.
>> Counting objects: 100% (20/20), done.
>> Delta compression using up to 12 threads
>> Compressing objects: 100% (10/10), done.
>> Writing objects: 100% (11/11), 1.56 KiB | 799.00 KiB/s, done.
>> Total 11 (delta 7), reused 0 (delta 0), pack-reused 0
>> remote: Resolving deltas: 100% (7/7), completed with 7 local objects.
>> remote: Bypassed rule violations for refs/heads/main:
>> remote:
>> remote: - Changes must be made through a pull request.
>> remote:
>> To github.com:elx-onlinx/beautychat-chatcards.git
>>    ffe1e05..bb7b0ef  main -> main
>> ```
>>
>> Having the link in the console saves me tremendous time and is
>> extremely effective/efficient. Can we get links in the console plz?
>>
>
> If we look very carfully at the log, we see that all the messages prefixed
> with "remote:" come from the remote (git server).
> In your case github. Other "Git repo servers" like gitlab or bitbucket have
> the same feature.
>
> Git itself, running on your local computer, does not produce this links.
> If you really want to push directly to the main branch and want to see the
> a link, then you better talk to the gihub folks.

Thanks for a good suggestion.

Another piece of advice we may want to give is that a good bugreport should illustrate both good and bad case. With only the above one, I couldn't guess that the complaint was about lack of information that comes over the wire from remote, *exactly* because the report failed to show the good case that shows the information and made the readers guess what thing that does not exist in the output is being complained about. A good bugreport should not force readers guess.

If the report had both good and bad cases, it would have helped readers help the reporter much easier.

Thanks.