Skip to content

Push generates no common ancestry #10

Description

@syntonyze

When pushing to a remote git returns a 'no common ancestry' error.
This is due to the fact gatling initializes an empty repository, sets a remote and then pushes a new change without ever fetching any ref.
The generated commit should be based on a parent commit that is already in the repo (i.e. master).

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