bug: origin refs updated too soon locally

From: Perry Wagle <wagle@cs.indiana.edu>
Date: Oct 18, 2007, 01:35 UTC
Message-ID: <8CEF6150-4BE7-4B4D-B58C-12CE4671007E@cs.indiana.edu>

If I clone a remote repository, make a few commits, push them to the remote repository, and the update hook on the remote repository rejects them (exit 1), the local origin refs are still updated as if the push had gone through. The workaround is to do a pull to set the origin refs back.

-- Perry

$ 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.