3 months ago
Hello,
I am experiencing an issue where new commits pushed to my GitHub repository are not triggering deployments on Railway.
Details:
- I am currently using the Railway free tier.
- My project is connected to my GitHub repository.
- I have pushed multiple commits to the repository, but Railway is not detecting the new changes and no new deployments are triggered.
- The service appears to still be connected to GitHub, but the pushes are not reflecting in the Deployments tab.
Could you please help determine whether this issue is related to:
- Free tier usage limits
- A GitHub webhook issue
- Or a deployment configuration problem?
Thank you for your assistance.
2 Replies
3 months ago
Please verify that your service's trigger branch in Service Settings matches the branch you're pushing to, and check that the GitHub App installation still has access to your repository at github.com/settings/installations. You can also try disconnecting and reconnecting the repo in your service settings, or manually deploying via the Command Palette (Cmd/Ctrl + K, then "Deploy Latest Commit") to confirm the connection is working. More details are in our GitHub Autodeploys docs.
Status changed to Awaiting User Response Railway • 3 months ago
Railway
Please verify that your service's trigger branch in Service Settings matches the branch you're pushing to, and check that the GitHub App installation still has access to your repository at [github.com/settings/installations](https://github.com/settings/installations). You can also try disconnecting and reconnecting the repo in your service settings, or manually deploying via the Command Palette (Cmd/Ctrl + K, then "Deploy Latest Commit") to confirm the connection is working. More details are in our [GitHub Autodeploys docs](https://docs.railway.com/deployments/github-autodeploys).
3 months ago
Fixed. Thanks
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved mcwaves3010 • 3 months ago