Skip to content
GitHub Auto-Deploy Not Triggering for Production API
lawrencelaxman1-arch
OP

a month ago

Hello Railway Support,

My Railway project is not triggering deployments for new commits pushed to GitHub.

Project: sri-ayyappa-rental-agency

Environment: production

Service: api

Repository: lawrencelaxman1-arch/sri-ayyappa-rental-agency-

Branch: main

Current deployed commit: e3bc6f2

Latest GitHub main commit: 9b28cfd

I verified the following:

  • The GitHub repository and main branch are correctly connected.
  • Railway Auto-Deploy is enabled.
  • Root directory is "/".
  • The Railway GitHub App is installed and has access to all repositories.
  • GitHub reports successful Vercel checks for commits 096560c and 9b28cfd.
  • Railway has no deployment status for either commit.
  • Railway's integration still reports status updates for the older commit, e3bc6f2.
  • The existing API service is online.

Could you please inspect the GitHub webhook delivery and Railway deployment-event processing logs for this service, and identify why new pushes are not triggering deployments?

I have not changed production settings or manually triggered a deployment.

Thank you.

Solved

1 Reply

Railway
BOT

a month ago

We checked the api service in production: it is connected to your repository with the root directory set to "/", and right now there are no builds or deployments queued, pending, or in progress in your workspace, so the pushes for 096560c and 9b28cfd did not create any deployment on our side, not even one waiting in the queue.

One thing worth checking in the service's settings is the source section, to confirm main is still selected as the trigger branch. Auto-deploys only fire for pushes to the branch that is set there.

If the repository is private, a push from a GitHub account that is not linked to a Railway account in this project or workspace creates a deployment that waits for approval rather than rolling out. Linking that GitHub account to a Railway account that is a member of the project or workspace removes the approval step for future pushes.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

23 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...