Hello @metricmogul You've gone through quite a bit of effort to troubleshoot the deployment issue on your end -- would you mind raising a support case so we can investigate this further?

We look forward to hearing from you!

Thanks for sharing the things you already checked! I have one more idea.

Sometimes this kind of problem is caused by a configuration error that makes the build fail before it even starts. There might be an error noted on the commit on GitHub, but you can also get more details with the CLI. You can run the vercel build command and it'll output error info if something is wrong with the build. You can also use the CLI to start a new deployment.

Thank you both for the responses. I'll try both of these tomorrow morning and let you know. It's good to know I can deploy via the CLI as a backup.

Just a quick update.

• I used the command line to build with no errors, and then push that to Vercel. I hadn't realised it was possible to do this so thank you @amyegan for letting me know that was possible, much appreciated. The deployment worked successfully.
• I've opened a Support Ticket regarding commits to Git not being deployed automatically. I re-tested a commit this morning and still no joy. I wasn't sure what information to add to the support ticket so I linked them to this thread.

Thanks again for your rapid support. I love the team at Vercel and the platform you offer!

Hi,

Could you confirm if this settings are intact : https://vercel.com/guides/why-aren-t-commits-triggering-deployments-on-vercel ? Could you also share an affected commit SHA which we can take a closer look?

Hi swarnava. Please see my first message above where I list out what I have tried.

Where do I find the commit SHA?

Hi,

You can review this instruction here to find commit SHA of your deployment: https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits

Ah I see, it's the commit number. Here's an example commit ID: 82193a1. This is one I commited about 5 minutes ago but has not been deployed automatically.

I will push it manually now using the process described above.

Can you share the full commit SHA? it usually contains 40 characters.

Hey @metricmogul! 👋

Just wanted to follow up here. If you've found a solution or still need help, let us know! We're happy to continue assisting.