Skip to content

Wrong tracking branch when re-cloning #533

Closed
@ghost

Description

Assume I have a repo foo that I want to clone into bar/copy. Let's say foo has two tagged commits v1 and v2.

When I first clone v1 using git subrepo clone --branch v1 copy and then later git subrepo clone --branch v2 --force copy and I check git subrepo status it tells me that Tracking Branch is v1. Is this intentional? I (maybe naively) assumed clone --force would have the same effect as me manually deleting copy and then doing a regular clone in which case Tracking Branch correctly says v2.

Side note:
When I use git subrepo pull --force --branch v2 copy everything seems to work. Can anyone fill me in what the differences between clone --force and pull --force are when used with branches?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions