Skip to content
Railway GitHub App: is a read-only source and CI permission profile available?
bryanbonmarchand
OP

a month ago

Hello,

Is there a supported least-privilege profile for the Railway GitHub App that allows reading repository contents and CI results without permission to modify repository code, workflows or repository administration?

  1. Which GitHub write permissions are required for source-based deployments, CI waiting and deployment/status reporting, and which are used only by optional features?
  2. Can an installer reduce individual installation permissions, or is a separate minimal-permission app or connector available?
  3. If Railway uses narrower installation tokens internally, can the underlying installation grant also be reduced?
  4. If there is no supported read-only profile, what is the documented alternative for delivering reviewed source code without granting GitHub code/workflow write access, and which integration features would it lose?

This is a general documentation question, unrelated to any particular project or service. It requests no changes, deployments, restarts, permission updates or subscription changes.

Thank you.

Solved

1 Reply

Railway
BOT

a month ago

We don't offer a read-only or least-privilege profile of the Railway GitHub App, and there is no separate minimal-permission app or connector. The app requests one fixed permission set, and installers can't reduce individual permissions on the installation. Any narrowing on our side is by repository, not by permission, so the underlying grant can't be reduced that way either. Repository selection in the GitHub installation settings is the scoping control that's available.

Broadly, the write access covers these features: commit statuses and GitHub deployment records report deploy progress back to commits, pull request and contents write support the Railway Agent's code changes and pull requests, and administration access is used to check which installations can write to a repository. Source deploys, Wait for CI, and PR environments all depend on the app being installed with its full permission set.

The alternative that needs no GitHub App access is to deploy reviewed code yourself, either with railway up from the CLI (for example from your own CI after review) or by deploying a prebuilt Docker image. With either option you lose automatic deploys on push, Wait for CI, PR environments, commit and deployment status reporting to GitHub, and the agent's pull request features.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

24 days 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 • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...