Cannot create PR main <- development: "A pull request already exists for BarcDevs:development" (HTTP 422), but no open PR exists #213771
Unanswered
BarcDevs
asked this question in
Pull Requests
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
Summary
In the public repo BarcDevs/Pulse--client, creating a pull request with base main and head development always fails with "A pull request already exists for BarcDevs:development". No open PR exists for that pair. The error persisted for about 40 minutes (roughly 15:50 to 16:30 UTC on 22 Nov 2026), so it is not a short cache delay.
Steps to reproduce
Repo: BarcDevs/Pulse--client (public). Default branch main, other branch development, same-repo PR.
(1) POST /repos/BarcDevs/Pulse--client/pulls with base=main and head=development. Repeat with head=BarcDevs:development.
(2) gh pr create --base main --head development (GraphQL createPullRequest).
(3) Web compare page flow for main...development.
Expected
A new PR is created, since no open PR exists for development -> main and the branch is ahead of main.
Actual
All three paths fail with HTTP 422 "Validation Failed", code "custom", message "A pull request already exists for BarcDevs:development".
Evidence
REST GET pulls?state=open returns 0 results.
GraphQL pullRequests(headRefName:"development") returns only MERGED PRs. The latest is #81, merged 2026-11-03, base main.
Search "is:pr head:development base:main" shows 0 open and 30 closed/merged.
Compare main...development shows ahead_by=27, behind_by=0 (able to merge). Before PR #92 (main into development) was merged at 2026-11-22T16:14:46Z it was ahead 26, behind 14, with a conflict only on the version line of package.json and package-lock.json. The error occurred both before and after that merge.
Workaround
I pushed a temporary branch release/client-edge at the same commit as development and opened PR #94 to main from it. It was created without error and merged. I then deleted the branch.
Impact
The normal development -> main release flow is blocked for this repo, and the only way around it is a throwaway branch. It looks like a stale "existing PR" uniqueness check for the head ref development, possibly tied to the earlier merged PRs from that same branch.
All reactions