Hi there. I was just wondering if anyone is experiencing Github commits not being deployed automatically since last night? My first three deployments worked fine, but after that Vercel is not picking up the latest commit.
There’s nothing in comments or logs anywhere to suggest why - it just seems not to be registering it.
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?
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.
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!
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.