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

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