When pushing to a remote, the creation ofPushInfo might fail, while the actual push was successful.
I got this on a forced update. git reports back with theold_sha...new_sha pattern, but since the remote was not fetched before, apparently the object database doesn't know the old (short) SHA and therefore fails to expand it forPushInfo instantiation, raisingBadName.
From my point of view, this should either not fail at all (since this is kind of a requirement for a push, that git itself doesn't rely on) or provide a more useful exception. If I callpush with a refspec like+local_branch:remote_branch, aBadName(5OM35H4) doesn't tell me, whether I need to deal with the exception or ignore it. At least I need to know, whether it refers to the local commit object (which should be known) or the remote one.

Edit: Forgot to mention: This happened to me in a test only after upgrading from gitpython 2.0.2 to 2.0.5