a month ago
Subject: GitHub App auto-creates a new project on every GitHub event ("via GitHub"), instead of deploying only to my existing service
Org: nexus-basketball (single member — only me)
Real project: fulfilling-reverence → service web, custom domain nexus.basketball, with a persistent volume. It's correctly connected to nexus-basketball/nexus-gestionale (branch main) with auto-deploy enabled.
Problem: New empty projects keep being created automatically. Each one contains a web service that deploys the exact same repo/commit and is explicitly labelled "via GitHub" in its deployment history. Recent examples: ravishing-joy, successful-flow, vibrant-spontaneity. They appear not only when I push, but also on other GitHub events I don't initiate (e.g. automation branches), so it looks random. Every push to main also deploys correctly to fulfilling-reverence — the ghost project is an unwanted duplicate on top of that.
Already checked / ruled out: no GitHub webhooks on the repo, no deploy CI/GitHub Actions doing this, no account or project API tokens, no templates, and I revoked the Railway CLI OAuth. The label is always "via GitHub", so it's the GitHub App integration — not a token or external API.
Request: Please stop new projects from being auto-created for GitHub events on this repo, so that pushes/events deploy only to fulfilling-reverence/web. Please tell me if there's a setting on my side, otherwise treat it as a bug in the GitHub App integration for my account. I can share project IDs on request.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
It's not the GitHub App, and there's no setting on your side causing it. Our audit log shows each of those projects was created from your own logged-in Railway session in Safari, not from a webhook, a token, or the GitHub integration. The "via GitHub" label only means that deployment came from a commit, it says nothing about what created the project.
One push looks like it spawns projects because each extra project has the same repo connected with auto deploy on. Your latest commit deployed to three of them inside the same second. The likeliest source is picking the repo from the New Project screen or command palette while you're not inside a project, which creates a fresh project instead of adding to the one you're viewing.
One thing was genuinely broken on our end. successful-flow wouldn't delete, and six attempts failed against a stuck internal record. That's cleared now, so it will delete. The other extra projects should delete normally, and once they're gone your pushes will only deploy to fulfilling-reverence.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved sam-a • about 1 month ago