Re: git fetch --prune fails with "fatal: bad object"

From: Fred Long <fred_long@fastmail.fm>
Date: Jun 4, 2024, 20:09 UTC
Message-ID: <876fbb07-210e-128e-5289-57ab01761750@fastmail.fm>
In-Reply-To: <20240604104437.GD1781455@coredump.intra.peff.net>

On 6/4/2024 3:44 AM, Jeff King peff-at-peff.net |git bugs/Example Allow| wrote:

Show 5 quoted lines

> In the case of a refs/remotes entry where you happen to know that you
> could re-clone from the other side, it is relatively low stakes. But I
> think keeping a human brain in the loop between corruption and deletion
> is a good thing. Corruption should not be happening so often that it's a
> major pain point.

In my case it's not corruption. It's people creating branches, deleting them, and then removing the commits. (Maybe our git server has an option to automatically prune commits that are not reachable from a branch or tag, I don't know.) But this happens very frequently at my work.