Skip to content

Clarify GitHub deploy approval prompts #1161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
radiantjade wants to merge 1 commit into from
Closed

Clarify GitHub deploy approval prompts #1161

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions content/docs/deployments/github-autodeploys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,18 @@ Public repositories where no project member has contributor access cannot use au

If you cannot enable autodeploy, see [Troubleshooting](#troubleshooting).

### External contributor approval prompt

Railway may ask you to approve a commit with the prompt **Deploy this commit from an external contributor?** when the commit author is not recognized as a project member who can deploy from the linked GitHub repository.

Repository ownership and GitHub App access are not the only checks. To skip the approval prompt for future commits, make sure that:

1. The Railway project includes a member with the [Deployer role or higher](/projects/workspaces#inviting-members).
2. That member has connected the GitHub account that authors the commits.
3. That GitHub account has contributor access to the linked repository.

After changing membership, GitHub permissions, or the linked GitHub account, disconnect and reconnect the repository in the service settings if Railway keeps prompting for approval.


## Wait for CI

Expand Down
Loading