Description
The create_pull_request action is not creating a pull request as expected.
Instead, it returns a patch file in the response.
This issue appears consistently when the repository already has more than one open pull request.
Expected Behavior
A new pull request should be created in the repository
The response should include PR details (URL, number, etc.)
Actual Behavior
No pull request is created
The action returns a patch file instead
Steps to Reproduce
Use a repository that already has multiple open pull requests
Trigger create_pull_request
Observe the response
Environment
GitHub Actions / Agentic workflow
Using safe-outputs.create_pull_request
Notes
This does not happen consistently in repos with zero or one PR
Seems related to how the action handles existing PR state
No explicit error is thrown
Impact
This blocks automated PR workflows, especially in multi-PR environments.
Description
The create_pull_request action is not creating a pull request as expected.
Instead, it returns a patch file in the response.
This issue appears consistently when the repository already has more than one open pull request.
Expected Behavior
A new pull request should be created in the repository
The response should include PR details (URL, number, etc.)
Actual Behavior
No pull request is created
The action returns a patch file instead
Steps to Reproduce
Use a repository that already has multiple open pull requests
Trigger create_pull_request
Observe the response
Environment
GitHub Actions / Agentic workflow
Using safe-outputs.create_pull_request
Notes
This does not happen consistently in repos with zero or one PR
Seems related to how the action handles existing PR state
No explicit error is thrown
Impact
This blocks automated PR workflows, especially in multi-PR environments.