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

From: Fred Long <fred_long@fastmail.fm>
Date: Jun 5, 2024, 23:43 UTC
Message-ID: <c2a02982-40a9-6629-05c2-c8de3335f35b@fastmail.fm>
In-Reply-To: <20240605084718.GD2345232@coredump.intra.peff.net>

On 6/5/2024 1:47 AM, Jeff King wrote:

Show 6 quoted lines

>
> Your local refs should not point to missing objects, though. Each clone
> should maintain its own consistency. Are you using "git clone --shared"
> or another scheme involving alternates?
>
> -Peff

I use Google's "repo" script to manage Android repositories. The "repo" script runs "git repack -a -d", and I think that's what's removing the commits locally. Remotely, our bitbucket server removes commits that are no longer referenced.