Skip to content

Force pushes can lead to "bad object" message from git rev-list #3977

@bk2204

Description

@bk2204

Describe the bug
When force-pushing a ref to a remote, if the object the remote side's ref points to is not in the local copy, we'll abort with a message like the following:

ref temp:: Error in git rev-list --stdin --objects --not --remotes=origin --: exit status 128 fatal: bad object ae86523521e10b0e8aa3c50dda910064ec2ff155

Expected behavior
We don't abort in this case and simply skip using that object.

System environment
Debian sid, Git LFS master

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions