Merging blocked by missing successful deployment even though deployment was successful, and GitHub knows it #76616
Replies: 2 comments 10 replies
-
Beta Was this translation helpful? Give feedback.
-
|
This page is 404 now. Any luck on finding the fix? |
Beta Was this translation helpful? Give feedback.
-
|
It seems like you're encountering an issue on GitHub related to a successful Preview deployment not reflecting in the merge status, preventing you from completing the merge. To address this bug, follow these steps: Check Deployment Status: Verify that the deployment GitHub shows as successful is indeed reflected in the GitHub interface. Ensure that your repository settings and branch protection rules are configured correctly. Sometimes, the interface might not update in real-time. Try refreshing the page to see if the correct status is reflected. If your deployment is part of a GitHub Actions workflow, review the workflow file to ensure it is correctly configured. Visit GitHub's status page to check if there are any ongoing incidents or outages affecting deployments. Clear your browser cache to ensure that you are viewing the most up-to-date information. If possible, try re-deploying or triggering a new deployment to see if it updates the deployment status. If the issue persists and none of the above steps resolve it, consider reaching out to GitHub Support for assistance. Provide them with relevant details and screenshots to help them understand the problem. Detailed steps to reproduce the issue. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same problem, i think there's a capitalisation issue. However, when trying to rename the branch it says it already exists (so ignoring capitalisation). I'm just having to force merge at this point, any idea on how to resolve (except for set the whole thing up again using lower case branch names and rules?) |
Beta Was this translation helpful? Give feedback.
-
|
This has started happening to us also, and now have to force merge. It happens every time so now I'm just turning off the checks, which is risky but we can't keep having these hold-ups, it's crazy. |
Beta Was this translation helpful? Give feedback.
-
|
As this is only in 'discussions' how can I check if this is recorded as an official bug? Is it an official bug? Surely must be since several people have no encountered it. But is it specific to Vercel I wonder? And therefore a bug with them and not with github. |
Beta Was this translation helpful? Give feedback.
-
|
We are having this issue as well |
Beta Was this translation helpful? Give feedback.
-
|
Going to try the following. Wondering if anyone has had any success with any of these re-triggering Github to fetch the Preview Deployment status.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
Screenshot says it all. Successful Preview deployment reported at top, merging blocked by missing the deployment GitHub shows is successful.
Using Vercel GitHub integration - Vercel handled creating the environments for me in GitHub.
Beta Was this translation helpful? Give feedback.
All reactions