{"thread":{"id":"66197","subject":"request-pull prints false warning when given commit hash as argument","startedAt":"2026-08-20T05:25:48Z","lastAt":"2026-08-20T05:25:48Z","messageCount":1,"participants":["Gahtan nahdi"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"550861","messageId":"CAD2gDY0=heAhqP1wr8dcuXz0-sEim1M9gV6TMb=UCZJuSCDuyw@mail.gmail.com","threadId":"66197","inReplyTo":null,"subject":"request-pull prints false warning when given commit hash as argument","fromName":"Gahtan nahdi","fromEmail":"gahtansyarif@gmail.com","sentAt":"2026-08-20T05:25:31Z","receivedAt":"2026-08-20T05:25:48Z","isPatch":false,"body":"Hi,\n\nI noticed what appears to be a bug in git request-pull when the <ref>\nargument is given as a commit hash rather than a ref name.\n\nFor example i did this:\ngit request-pull 5a12652e\nhttps://github.com/gahtan-syarif/fast-chess.git 1ccb9f6e\nwhich caused git to produce a warning:\nwarn: No match for commit 1ccb9f6e66dc1eb7afa7bc782e7631b4fe39d505\nfound at https://github.com/gahtan-syarif/fast-chess.git\nwarn: Are you sure you pushed '1ccb9f6e' there?\n\nHowever, that commit does exist in the remote repository.\nThis only happens when I give it a commit hash in the arguments\ninstead of a ref-name.\nMight not be a major issue but I thought it's worth reporting nonetheless.\n\ngit version 2.43.0\n\nRegards,\nGahtan\n"}]}