Skip to content
Does disabling/enabling GitHub autodeploy trigger a deployment?
abdur1012141618
OP

an hour ago

We need clarification before a frontend-only release.

Our production service deploys automatically from GitHub main and

runs a database-changing pre-deploy command. We want to keep the

currently running backend unchanged while releasing the frontend.

Please confirm the current behavior:

  1. Does clicking “Disable automatic deployments” only change the

    Git trigger, or does it stage/apply a service change, create a

    deployment, restart the service, or run the pre-deploy command?

  2. Once disabled, does a push/merge to main create no deployment,

    or a skipped deployment? Does the existing service keep running?

    Does disabling affect already queued/in-progress deployments?

  3. Does clicking “Enable” immediately deploy the latest main commit,

    including commits received while disabled, or only react to

    future commits? Can enabling itself restart/redeploy the service?

Please provide a definitive answer or route this to a human reviewer.

We have not changed settings or performed this release.

Awaiting User Response

3 Replies

Railway
BOT

an hour ago

Clicking Disable stops the service from deploying automatically when new commits land on the connected branch. To deploy the latest commit while autodeploy is off, open the Command Palette (CMD + K) and select Deploy Latest Commit, which deploys the latest commit from the connected branch. See Controlling GitHub Autodeploys.

We can't give a definitive answer on the other points you asked about. Those are whether the toggle itself creates a deployment, restarts the service, or runs the pre-deploy command, how pushes made while autodeploy is off appear in history, what happens to queued or in-progress deployments, and whether clicking Enable deploys commits received while it was off. Since your pre-deploy command changes the database, please test the disable, push and enable sequence on a separate test service or environment before your production release.


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


Railway

Clicking **Disable** stops the service from deploying automatically when new commits land on the connected branch. To deploy the latest commit while autodeploy is off, open the Command Palette (`CMD + K`) and select **Deploy Latest Commit**, which deploys the latest commit from the connected branch. See [Controlling GitHub Autodeploys](https://docs.railway.com/deployments/github-autodeploys). We can't give a definitive answer on the other points you asked about. Those are whether the toggle itself creates a deployment, restarts the service, or runs the pre-deploy command, how pushes made while autodeploy is off appear in history, what happens to queued or in-progress deployments, and whether clicking **Enable** deploys commits received while it was off. Since your pre-deploy command changes the database, please test the disable, push and enable sequence on a separate test service or environment before your production release.

abdur1012141618
OP

an hour ago

Thanks. The documented purpose of Disable is clear, but the production

safety questions remain unresolved.

Please route this to a Railway staff member to confirm:

  1. Can Disable itself deploy/restart the service or run pre-deploy?
  2. What happens to queued or in-progress deployments?
  3. Does Enable trigger an immediate catch-up deployment?

I have not changed production settings. Testing in another environment

may provide observations, but it would not establish guaranteed

production behavior. Please keep this thread unresolved.


Status changed to Awaiting Railway Response Railway • about 1 hour ago


Railway
BOT

42 minutes ago

We understand you want certainty before touching production. What we can confirm is the documented behavior: Disable stops new commits on the connected branch from deploying automatically, Enable turns that back on, and while it is off you can deploy the latest commit manually with Deploy Latest Commit from the Command Palette (Controlling GitHub Autodeploys).

We can't provide staff or engineering confirmation of the additional toggle side effects you listed, so if your release depends on them, validating the disable, push and enable sequence on a separate test environment is the way to rely on it.


Status changed to Awaiting User Response Railway • 42 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...