threads / bug / 60528

Bug: "Received" misspelled in remote message

Subject: Bug: "Received" misspelled in remote message

## tl;dr

5 messages between Nov 15, 2023 and Nov 16, 2023.

replies: 4people: 4as markdown or json

Alan Dove· Nov 15, 2023, 18:46 UTC · lore

Hello:

Using Git 2.40.1 on a private server, I see this message whenever I push a commit:

"remote: Recieved update on checked-out branch, queueing deployment."

"Received" is misspelled.

I realize this is a very minor issue, but it should also be very easy to correct. As someone who suffers from Proofreader's Eye, this error deals psychic damage to me on a daily basis.

Thanks.

-- 
 --Alan

Alan Dove, Ph.D.
alandove.com
917.273.0544

Eric Wong· Nov 15, 2023, 19:26 UTC · re: Alan Dove · lore

Re: Bug: "Received" misspelled in remote message

Alan Dove <alan.dove@gmail.com> wrote:

Show 6 quoted lines

> Hello:
> 
> Using Git 2.40.1 on a private server, I see this message whenever I
> push a commit:
> 
> "remote: Recieved update on checked-out branch, queueing deployment."

Hi Alan, that's likely from a hook on the server itself. Those phrases aren't a part of git at all.

Konstantin Ryabitsev· Nov 15, 2023, 19:45 UTC · re: Alan Dove · lore

Re: Bug: "Received" misspelled in remote message

On Wed, Nov 15, 2023 at 01:46:10PM -0500, Alan Dove wrote:

Show 12 quoted lines

> Hello:
> 
> Using Git 2.40.1 on a private server, I see this message whenever I
> push a commit:
> 
> "remote: Recieved update on checked-out branch, queueing deployment."
> 
> "Received" is misspelled. 
> 
> I realize this is a very minor issue, but it should also be very easy
> to correct. As someone who suffers from Proofreader's Eye, this error
> deals psychic damage to me on a daily basis.

It's most likely coming from some CI/CD hook deployed on the server where you're pushing, so you should reach out to your IT to have the spelling fixed.

In other words, the message is not coming from any software that is managed by the git project itself (at least, nothing matches "recieved" in the git repository tree).

Best regards, -K

Junio C Hamano· Nov 16, 2023, 03:10 UTC · re: Alan Dove · lore

Re: Bug: "Received" misspelled in remote message

Alan Dove <alan.dove@gmail.com> writes:

Show 8 quoted lines

> Hello:
>
> Using Git 2.40.1 on a private server, I see this message whenever I
> push a commit:
>
> "remote: Recieved update on checked-out branch, queueing deployment."
>
> "Received" is misspelled.

I think it is coming from the "push-to-checkout" hook that is installed on your "private server", and not from what we ship as part of our software offering.

We are not going to include spelling correction software to massage the output from end-user installed hooks, so it is unlikely the typo will be fixed by us.

> I realize this is a very minor issue, but it should also be very easy
> to correct. As someone who suffers from Proofreader's Eye, this error
> deals psychic damage to me on a daily basis.

Sounds like something a world-class science writer may say ;-).

Thanks for reporting.

Junio C Hamano· Nov 16, 2023, 03:42 UTC · re: Junio C Hamano · lore

Re: Bug: "Received" misspelled in remote message

Junio C Hamano <gitster@pobox.com> writes:

Show 7 quoted lines

>> "remote: Recieved update on checked-out branch, queueing deployment."
>>
>> "Received" is misspelled. 
>
> I think it is coming from the "push-to-checkout" hook that is
> installed on your "private server", and not from what we ship as
> part of our software offering.

Googling for the misspelled message seems to indicate that it is coming from cpanel (whatever it is). A randomly picked example is https://essgeelabs.com/posts/cpanel-git-1/ which is a recipe that does not involve typing the typoed message by the end-user, so somebody (most likely cPanel) must be shipping with a hook with typo.

Another user of cPanel reports this

https://forums.cpanel.net/threads/git-automatic-deployment-not-working-but-manual-deployment-is.679837/

where they observe post-receive hook with the typo.

Anybody with contact there at cpanel.net may want to report the bug.

Thanks.