2 months ago
Hello, Railway team.
I am experiencing an issue with the integration between Railway and GitHub. Currently, after workflows run on GitHub (such as commits or CI pipelines), the automatic deploy on Railway is not being triggered as expected.
Problem details:
- The repository is correctly connected to Railway
- GitHub workflows are running normally
- However, Railway does not start the deploy automatically after these executions
Important note:
I recently changed the name of my GitHub organization and reinstalled/re-authorized the Railway app within GitHub.
What I have already checked:
- GitHub integration is active and linked to the correct project
- The correct branch is configured for deploy
- There are no visible errors in the GitHub logs
- The GitHub app permissions appear to be correct
Question:
Is there any additional configuration required to ensure that deploys are automatically triggered after GitHub workflows? Or could this be an issue related to the integration after the organization name change?
If needed, I can provide logs, screenshots, or access for further investigation.
Thank you.
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your GitHub integration is returning authentication errors ("Bad credentials") when we attempt to deploy, which is consistent with the organization rename and reinstallation you described. To fix this, go to GitHub Settings > Applications > Railway App > Configure and confirm the Railway app has access to your repositories under the new organization name. Then go to your Railway account settings and unlink and relink the GitHub integration. After that, you will also need to disconnect and reconnect the GitHub repo in each affected service's Settings > Service Source section, since the existing connections still reference the old organization path.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Hello,
Thank you for your guidance.
I followed all the steps you suggested:
- Verified the Railway app permissions in GitHub after the organization rename
- Unlinked and relinked the GitHub integration in Railway
- Disconnected and reconnected the repository in the service settings
However, the issue persisted. The integration still did not recognize the new organization name. When I attempted to trigger a deploy, Railway returned an error indicating that there was nothing to deploy, even though the service was correctly set up.
As a test, I reverted the GitHub organization name back to its original name, and everything started working normally again. Deploys were triggered as expected.
Based on this, it seems the issue is specifically related to the organization rename not being fully recognized by the integration.
For now, the problem is resolved on my side after reverting the name, but I wanted to report this behavior in case it helps improve the integration or identify a potential issue.
Please let me know if you need any additional information.
Thank you.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved johnnyboysou • about 2 months ago