a month ago
GitHub Auto Deploy remains unavailable with reason NO_REPO.
Project: c1e2aa8b-e064-4b24-8d81-08d26c567eb2
Environment: 93f0fc25-5269-498e-8704-5874d1d9ad8d
Service: 2387f3ad-9480-45fe-b68a-c3f50fe569d3
Repository: vboransin-star/jjblue-ai-production
Branch: main
Verified:
- Railway account is connected to GitHub as vboransin-star
- Railway GitHub App is installed
- Repository access is granted
- Updated GitHub permissions were accepted
- Repository was disconnected and reconnected
- Browser hard refresh and Railway cache refresh were performed
- Source repo and branch are visible and correct
- Auto Deploy still shows unavailable / NO_REPO
Production is healthy. Please resync the GitHub installation and auto-deploy eligibility for this service without modifying or deleting the active deployment.
1 Replies
a month ago
The repository connection is currently staged but has not been applied yet. Your service has 3 pending changes (the repo, branch, and check-suites setting) that were edited but never deployed. Until you click the Deploy button in the dashboard to apply those staged changes, the service has no source connected, which is why auto-deploy reports NO_REPO. Applying the staged changeset will connect the repo and restore auto-deploy without affecting your running deployment.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 1 month ago