5 days ago
Hello Railway Support!
I'm experiencing an issue with GitHub automatic deployments for my existing backend service.
Project details:
- Railway project: resplendent-insight
- Service: backend
- GitHub repository: gosfring111-coder/MW (private)
- Branch: main
- Root Directory: /backend
My account and permissions:
- GitHub account connected to Railway: gosfring111-coder
- Railway workspace role: Admin
- Railway GitHub App is installed on the correct GitHub account.
- The app has access to the MW repository.
- GitHub OAuth authorization is active.
Issue:
Railway displays "Auto deploy unavailable".
The tooltip says:
"No project member has access to this GitHub repository. Check if the GitHub Railway App is installed and project members have their GitHub accounts connected."
I found a similar support thread where a Railway employee recommended fully uninstalling and reinstalling the GitHub App.
I followed those instructions:
- Uninstalled Railway App from GitHub.
- Reinstalled it on the correct account.
- Granted access to the MW repository.
- Refreshed the repository list in Railway.
- Reconnected the repository to my existing backend service.
Unfortunately, the error persists.
Could you please investigate the GitHub identity association or repository installation binding on the Railway side?
I would like to enable automatic deployments without recreating my existing production service.
Please preserve the existing persistent volume, environment variables, database and domain.
Thank you!
1 Reply
5 days ago
The repository reconnection hasn't been applied to your backend service yet. In the production environment, the repo (gosfring111-coder/MW), branch main and root directory /backend are sitting as 3 staged, unapplied changes. Right now the service's saved configuration has no source connected at all, which is why auto deploy shows as unavailable.
To fix it, open the project canvas and apply (deploy) those staged changes. Once they're applied, the service will be linked to the repo and auto deploy should be available. This staged change only sets the source repo, branch and root directory. It doesn't touch the service's volume, variables or domain.
Status changed to Awaiting User Response Railway • 5 days ago