Unable to create 2 pull requests from the same branch

Subject of the issue

Attempt

Trying to create 2 PRs from the same branch

Result

One PR is created and instantly closed. (when the second PR is about to be created, the first one gets closed instead)

Expected

Two different PRs to be created

Steps to reproduce

1. Add these 2 steps to a workflow.

      - id: create_pr_to_development
        name: Create PR to development
        uses: peter-evans/create-pull-request@v4
        with:
          base: development
          branch: BRANCH_NAME
          delete-branch: false
          title: Merge `${{ env.branch_name }}` into `development`
          body: Automated PR from create-candidate github action. Merge this when candidate is released.

      - id: create_pr_to_main
        name: Create PR to main
        uses: peter-evans/create-pull-request@v4
        with:
          base: main
          branch: BRANCH_NAME
          delete-branch: false
          title: Merge `${{ env.branch_name }}` into `main`
          body: Automated PR from create-candidate github action. If you merge this, a new production build will be triggered.

1. Replace BRANCH_NAME with a branch that exists
2. Make sure branches main and development exists or rename those branches above 👆

[peter-evans]

@oliversalzburg I’ve worked on an enhancement to the action to support your use case. It’s a potentially breaking behaviour change for the action, so I will need to release it as a new major version. Until the release, you can use the beta version with tag v5-beta.

You should be able to do this in your workflow now:

- uses: peter-evans/create-pull-request@v5-beta
  with:
    add-paths: |
      ./packages/payment-models/index.d.mts
    branch: feat/update-tsd
    
- uses: peter-evans/create-pull-request@v5-beta
  with:
    add-paths: |
      ./packages/infrastructure/lambda-schema.yaml
    branch: feat/update-openapi-components

(I removed setting the base explicitly because it should be unnecessary if you are already checked out on the next branch when the action executes)

[oliversalzburg]

Oh nice! Seems like I missed the earlier notification.

Right now, we’re using multiple workflows, and already build a lot of stuff around that approach now. The pipelines I was working on earlier, served as blueprints for another team who is now in charge of handling all the CI.

As I am using your action in a lot of places, I am very likely to get back to this though. I very much appreciate you looking into this and I will share my feedback once I have it 😃