It does not upload your local folder again. Clicking Deploy on staged changes redeploys the affected service, and a redeploy reuses the code from your most recent deployment (the last railway up) rather than uploading new code, so only your updated Healthcheck Path and Restart Policy change.

The relevant docs are Staged Changes and railway redeploy, which redeploys the latest deployment without uploading new code if you would rather trigger it from the CLI.

Thanks. Could a Railway team member please confirm this in writing? The answer above says a dashboard Deploy reuses the code from the last railway up and doesn't upload the folder again. The Staged Changes docs don't say that, so I'd like a person to confirm it before I rely on it. Thank you.

Confirmed: your local folder is not uploaded again. The Staged Changes page says that clicking Deploy applies all the changes at once and redeploys any affected services. The railway redeploy page describes a redeploy as redeploying the most recent deployment without uploading new code. So your service is deployed again with the code from your last railway up, plus the new Healthcheck Path and Restart Policy.

One more detail: a redeploy creates a new deployment from that same source and runs a build, so it does not reuse the previous deployment's image as is. The command that reuses the existing image with no build is railway restart, but it only restarts the current deployment. A redeploy is what applies new settings.