Skip to content

Clarify GitHub deploy approval prompts#1161

Closed
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-github-deploy-approval
Closed

Clarify GitHub deploy approval prompts#1161
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-github-deploy-approval

Conversation

@radiantjade
Copy link
Copy Markdown
Contributor

Summary

  • Document when Railway shows the "Deploy this commit from an external contributor?" approval prompt.
  • Clarify that repository ownership and GitHub App access are not the only checks; the commit author also needs to map to a Railway project member with deploy permissions and a connected GitHub account.
  • Point users to reconnect the repository after membership or GitHub identity changes.

Related Central Station bounty: https://station.railway.com/questions/external-contributor-prompt-on-every-p-5629e344

Testing

  • git diff --check
  • pnpm exec content-collections build

Autodeploy troubleshooting already documented the repository permission requirements, but the approval prompt path did not explain that Railway also checks the Railway project member and connected GitHub identity. Add the missing explanation near the autodeploy requirements so affected users can fix membership or reconnect the repository before contacting support.

Constraint: Central Station bounty asks what Railway checks before auto-deploying repo-owner commits
Rejected: Add a separate troubleshooting page | one short section in the existing autodeploy page is easier to find
Confidence: medium
Scope-risk: narrow
Tested: git diff --check; pnpm exec content-collections build
@brody192 brody192 closed this May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants