Skip to content

Add challenges for "git merge" #4

@sochotnicky

Description

@sochotnicky

There should likely be multiple scenarios - including failed merge due to conflicts. And ideally the conflicts would also semantically conflict so it would show the need to think and not merge blindly.

Another challenge should show that dependencies won't necessarily show up during merge (i.e merge will go OK, but testsuite will fail).

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