Automatic deployments via GitHub on each new commit are no longer working
erwang64
PROOP

2 months ago

Hello,

Since yesterday, for all my services, each new commit pushed via GitHub no longer triggers automatic deployment. I have to launch it manually using CTRL+K and “deploy last commit.”

What I have tried:

  • Disconnecting and reconnecting the repository and branch
  • Creating a new service
  • Uninstalling and reinstalling the Railway GitHub app on GitHub

Thank you in advance!

Solved

3 Replies

chandrika
EMPLOYEE

2 months ago

Hi there, could you please provide a link to the project / services you are seeing this in?


Status changed to Awaiting User Response Railway 2 months ago


erwang64
PROOP

2 months ago

Hello :

c1e0b6d3-0288-4211-9f11-78f935f0cdd1


Status changed to Awaiting Railway Response Railway 2 months ago


sam-a
EMPLOYEE

2 months ago

Thanks for providing the project ID. This is a known issue that can occur after uninstalling and reinstalling the Railway GitHub App.

When the GitHub App is uninstalled, the internal deployment triggers get deleted. Reinstalling the app does not automatically recreate these triggers.

To fix this, disconnect and reconnect the repository at the service level:

  1. Go to your service's Settings, then Source
  2. Disconnect the repository
  3. Reconnect it, selecting the same repo and branch
  4. Repeat for each affected service

If you see an error about GitHub access being revoked when trying to reconnect, you may also need to reconnect your GitHub account in Account Settings, then Connected Accounts.

After reconnecting, push a test commit to verify auto-deploys are working again.


Status changed to Awaiting User Response Railway 2 months ago


Railway
BOT

2 months 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 about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...