Merging blocked by missing successful deployment even though deployment was successful, and GitHub knows it

[prplecake]

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.

[prplecake]

See also https://github.com/orgs/vercel/discussions/1886

[harshai07]

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.
Confirm the status of the deployment matches the reported success.
Review Repository Settings:

Ensure that your repository settings and branch protection rules are configured correctly.
Check if there are any specific requirements or conditions for merging, such as required checks or deployments.
Refresh the Page:

Sometimes, the interface might not update in real-time. Try refreshing the page to see if the correct status is reflected.
Review GitHub Actions Workflow:

If your deployment is part of a GitHub Actions workflow, review the workflow file to ensure it is correctly configured.
Check for any errors or warnings in the GitHub Actions logs.
Check GitHub Status:

Visit GitHub's status page to check if there are any ongoing incidents or outages affecting deployments.
Clear Browser Cache:

Clear your browser cache to ensure that you are viewing the most up-to-date information.
Re-deploy or Trigger Deployment:

If possible, try re-deploying or triggering a new deployment to see if it updates the deployment status.
Contact GitHub Support:

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.
When reporting the bug to GitHub Support, be sure to include:

Detailed steps to reproduce the issue.
The exact error message or unexpected behavior you are encountering.
Any relevant screenshots or error logs.
Remember that GitHub's support team is generally responsive and can provide targeted assistance based on the specifics of your case.

[Bloke-Bloke]

change preview to lowercase

[Bhushan-WhiteBoxData]

Any luck with this @prplecake ? This seems to have been an issue for us since yesterday. We haven't made any changes at all on Github or Vercel which we use for deployment.
We even recreated the PR multiple times to see if it would resolve but no luck so far! This is a major blocker for us.

Also, are there any downsides to Force Merging the PR?

[reefbreak]

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?)

[rmcsharry]

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.

[rmcsharry]

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.