Peter Evans

If anyone is following this development and is willing to test it, you can find documentation [here](https://github.com/peter-evans/create-pull-request/blob/signed-commits/docs/concepts-guidelines.md#commit-signature-verification-for-bots). Just replace the version of the action with the branch name of this...

Hi @devjorgecastro Please do what I suggested [here](https://github.com/peter-evans/create-pull-request/issues/3237#issuecomment-2305261026) and remove the unnecessary steps. I want to confirm that you aren't seeing this conflict because of those steps.

I'm not sure if this is the cause of the problem, but because you are creating two pull requests, the branches need to be unique. ```diff -branch: release/${{ inputs.version-name }}...

Did you make [this change](https://github.com/peter-evans/create-pull-request/issues/3241#issuecomment-2307235042), and are still seeing an issue?

> and the requirement I have is to keep the same branch for the two pull requests I don't think that is going to work. I'm fairly sure that a...

I'm almost certain this is not going to work unless you make two separate branches as suggested [here](https://github.com/peter-evans/create-pull-request/issues/3241#issuecomment-2307235042).

Closing this for now. Feel free to continue the conversation if you need to.

Hi @paymog I'm not really sure. It might be possible to "reset" by recreating the `dev` branch on the HEAD of `prod` and trying again. Or you could click to...

Hi @laeubi This is very strange because it looks like [this run](https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/actions/runs/10379045649) ran against the correct commit on master with the changes you merged. The action thinks there is no...

Oh wait. I see what's happening now. I think you've run into an edge case that I've not considered. Partially merging content from within a single commit. There is no...