We've been investigating why auto-deploys and PR environments silently stop triggering, and have traced it to upstream GitHub API requests not being handled gracefully on our end. We've shipped additional monitoring to measure the false positive rate and pinpoint exactly where the issue lies. We'll follow up once we land a core fix. In the meantime, disconnecting and reconnecting your repo at the service level (Settings > Source Repo) is the best workaround. Sorry for the trouble.

Hi, I'm investigating reports for this topic, and I've noticed that the Railway GitHub App Installation for your organization is missing permissions that we updated a few weeks/months ago. They need your approval.

Could you please do the following:

1. Go to your GitHub Organization Settings
2. In the sidebar, find Third-Party Access -> GitHub Apps
3. In the list of installed GitHub Apps, find "Railway App". You should see it saying "Permission updates requested"
4. Click on "Review request" and accept the new permissions
5. Then reconnect the services that are not auto-deploying

We require these permissions to continuously check that your workspace has access to the repo. Without these permissions, our system can't verify access, and will not auto-deploy. This is a safety measure to prevent that someone who used to have access to the repo, but has no access anymore, could still deploy your repo, and thus would still have access to your code.

You should've gotten an email from GitHub when we updated the permissions, prompting you to review them. We will work on showing this notification in our Dashboard as well. Apologies for the friction this caused.