2 months ago
Since roughly the time of GitHub's major outage on 2026-08-17, no push creates a deployment. Every service in my project is pinned to the last commit Railway saw before the outage. My branches are now several commits ahead. There is no error anywhere - Railway simply does nothing.
Everything I've ruled out:
- Wait for CI - off.
- Re-selecting the branch in Settings → Source - no effect (it re-saves the setting, it doesn't force a fetch).
- Fresh pushes - three of them, all well after GitHub returned to "All Systems Operational". Including an empty commit pushed purely to generate a clean webhook event. No pickup.
- Source Repo disconnect + reconnect - did it, re-selected the branch. Still nothing.
- GitHub App installation - verified healthy: installed, scoped to the repo, with read/write on code, deployments, checks and workflows.
- Auto deploys - enabled.
Possible clue: right after reconnecting, the branch dropdown auto-populated to master and a deploy button was active. Switching the dropdown to my actual deploy branch made the button disappear entirely. It looks like Railway has a ref fetched for one branch and nothing for the other, and never resolves it.
The part that makes this hard to escape: railway redeploy re-runs the existing deployment's commit, so it just rebuilds the stale one. There seems to be no CLI way to say "build the current HEAD of this branch."
Questions:
- Did anyone else's Railway stop ingesting commits after the Aug 17 GitHub outage, and what cleared it?
- Is there any supported way to force a build of a specific/latest commit?
- Does railway up permanently convert a GitHub-source service to a CLI-source one, or is it safe as a one-off bypass?
1 Replies
2 months ago
Apologies for the trouble. We had an incident affecting GitHub auto-deploys on Aug 17, which has since been resolved. You can see the full timeline here: status.railway.com/incident/W4MIGEVT. Your services are receiving pushes now, but the recent deployments are landing as SKIPPED because your services have watch paths configured (e.g. /packages/web/** on the web service). When a commit does not touch files matching the watch path, the deployment is created but immediately skipped, and empty commits never match a watch path, so those are skipped too. You can confirm this by clicking "Show Skipped" in the deployment history. To force a build of the latest commit right now, open the Command Palette (CMD + K or Ctrl + K) and choose "Deploy Latest Commit", which always rebuilds regardless of watch paths. Regarding railway up, it changes the service's source to a CLI upload and disconnects the GitHub repo, so it is not safe as a one-off bypass if you want to keep auto-deploys.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved rayveera • about 2 months ago