Troubleshooting PR creation failure
See original GitHub issueI’m currently trying to mitigate this issue:
Checking if dotnet/aspnet 6.0.11-alpine3.16 needs updating
Requirements to unlock own
Updating dotnet/aspnet from 6.0.11-alpine3.16 to 6.0.12-alpine3.16
Submitting dotnet/aspnet pull request for creation. Failed! PR already exists or an error has occurred.
However, the permissions look good based on the docs here:
Any further tips how to fix this? There are no open PRs.
Issue Analytics
- State:
- Created 9 months ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Error while creating PR
Hi,. While creating PR, I have entered all value and if i click check it is giving message that no messages during check....
Read more >Error on Purchase Requisition creation - Enterprise Software
Hi all, I have a problem when creating a Purchase Requisition with Item Category M. The error message is ""Field Selection PT4B not ......
Read more >Troubleshooting Common Queries: Purchase Orders and ...
This article details various troubleshooting tips and areas to check regarding issues with Purchase Orders & Requisitions within Purchasing & ...
Read more >Error: "No instance of object type PurchaseRequisition has ...
Issue. While creating Service Requisition from Ariba P2P to SAP ECC, the below error is thrown from SAP: No instance of object type...
Read more >SAP message CO876 Error occurred during creation of pur
The system cannot generate the corresponding purchase requisition. How to fix this error? Check the affected operation and enter the data still required,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That was it, it might be good to improve the logs there though.
With #438 you may have better visibility into the requests and responses for HTTP