git/list[1] front-page[2] threads[3] people[4] search[5] about
 

request-pull prints false warning when given commit hash as argument

From
GNGahtan nahdi <gahtansyarif@gmail.com>
Date
Aug 20, 2026, 05:25 UTC
Message-ID
<CAD2gDY0=heAhqP1wr8dcuXz0-sEim1M9gV6TMb=UCZJuSCDuyw@mail.gmail.com>
Hi,

I noticed what appears to be a bug in git request-pull when the <ref> argument is given as a commit hash rather than a ref name.

For example i did this: git request-pull 5a12652e https://github.com/gahtan-syarif/fast-chess.git 1ccb9f6e which caused git to produce a warning: warn: No match for commit 1ccb9f6e66dc1eb7afa7bc782e7631b4fe39d505 found at https://github.com/gahtan-syarif/fast-chess.git warn: Are you sure you pushed '1ccb9f6e' there?

However, that commit does exist in the remote repository. This only happens when I give it a commit hash in the arguments instead of a ref-name. Might not be a major issue but I thought it's worth reporting nonetheless.

git version 2.43.0

Regards, Gahtan

Message 1 of 1 in “request-pull prints false warning when given commit hash as argument”
  1. Gahtan nahdiAug 20, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.