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

[fredg02]

https://github.com/eclipse-cbi/eclipse-cbi-tycho-example/pull/10 contains 23 commits.

The first two commits are fine and expected:

• https://github.com/eclipse-cbi/eclipse-cbi-tycho-example/pull/10/commits/a6905c7899af02ffee9e4763e2e38ea5ca591cff
• https://github.com/eclipse-cbi/eclipse-cbi-tycho-example/pull/10/commits/3a4060c45efd028779af296a020f2bd0e0d5dd9a

The next commit is a bit odd:

• https://github.com/eclipse-cbi/eclipse-cbi-tycho-example/pull/10/commits/1663f25c948ea1c091eff4acffd693d0b677f66b

Instead of rebasing the first two commits on the latest HEAD commit, a new commit has been created that is identical to https://github.com/eclipse-cbi/eclipse-cbi-tycho-example/pull/10/commits/1663f25c948ea1c091eff4acffd693d0b677f66b.

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.