Skip to content

Automatic PRs for pinning workflows are going a bit off the rails #530

@fredg02

Description

@fredg02

eclipse-cbi/eclipse-cbi-tycho-example#10 contains 23 commits.

The first two commits are fine and expected:

The next commit is a bit odd:

Instead of rebasing the first two commits on the latest HEAD commit, a new commit has been created that is identical to eclipse-cbi/eclipse-cbi-tycho-example@1663f25.

Since nobody merged the PR yet, this keeps happening. @heurtematte noticed this first.

I'd recommend rebasing the commits, so only the actual "pinning" requests are left in such PRs.

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