Skip to content
Request: allow auto-deploy for commits from an outside contributor on a Hobby workspace project
yj7
OP

9 days ago

Problem and desired outcome

I run a small production Django app on Railway on the Hobby plan, deployed from a GitHub repository with auto-deploy on push. Commits pushed by a second contributor, who is not a member of my Railway workspace, do not auto-deploy; only my own commits do. I understand this is a Hobby plan restriction and that Railway can override it for a project on request. I would like that override applied to this project so that pushes to the deployment branch deploy automatically regardless of which of the two of us authored them.

The impact is that every change from the other contributor waits until I manually redeploy or push a commit myself. This is ongoing.

Resources and timing

  • Workspace- Hobby plan
  • Project: insightful-exploration
  • Environment: production
  • Services affected: the web service, plus the cron services that deploy from the same repository (six job services and cron-pg-backup)
  • GitHub repository: Jhunjhunwala-Advisors/GIC-Django (deployment branch: master)
  • Custom domain: jhunjhunwalaadvisors.com
  • Contributor whose commits are not auto-deployed: GitHub user VaibhavJhunjhunwala

I decided to contact support myself. My understanding is that auto-deploy for contributors outside the workspace is not available on the Hobby plan, and that Railway can override this setting on request. This is a setting I cannot change from the dashboard, so I am asking Railway to enable it for this project.

Uncertainty and constraints

  • That this is a Hobby plan restriction, and that an override is available on request, is my understanding rather than something I have confirmed in Railway's documentation. If the override is not possible, please let me know what the supported options are on the Hobby plan.

Prepared with Railway's support template (v1).

Solved

3 Replies

Railway
BOT

9 days ago

Our records don't show this as a Hobby plan restriction with an override available on request. When the repository is private and a commit is pushed by a GitHub account that isn't a trusted member of the project, the deployment waits for approval instead of rolling out. That's a safety feature, and it applies on every plan.

To make that contributor's pushes deploy automatically, they need to link their GitHub account (VaibhavJhunjhunwala) to a Railway account, and that Railway account needs to be a member of the project or the workspace. Either one is enough. The deploy source view has an "Invite to workspace" action for this.

After that, future pushes from them deploy without the approval step. Any deployment that's already waiting still has to be approved once from the deployments list. Public repositories never need this approval.


Status changed to Awaiting User Response Railway • 9 days ago


yj7
OP

9 days ago

But invite to workspace is not allowed in the hobby plan


Status changed to Awaiting Railway Response Railway • 9 days ago


Railway
BOT

9 days ago

Joining the workspace isn't required. Membership of the project itself is enough. Once your contributor has linked their GitHub account to a Railway account and that account is a member of the project, their pushes to a private repository deploy automatically, with no approval step.

To add them, open the project's Settings and go to the Members tab. You can invite them by email or send them an invite link. Give them the Editor scope, because Viewers can't make deploys. Any deployment that's already waiting still needs to be approved once from the deployments list.


Status changed to Awaiting User Response Railway • 9 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...