Skip to content

Ancestry path fails if there are no .gitrepo file #306

Closed
@grimmySwe

Description

@grimmySwe

When I attempted to push my latest change I got a lot of fatals claiming bad commit objects. This was due to a merge with a branch that didn't have the subrepo.

fatal: 4b825dc642cb6eb9a060e54bf8d69288fbee4904 is not a valid 'commit' object

Looking into removing these error messages as they can be quite disturbing.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions