Skip to main content
Repository sync does not by itself deploy a service. Opt in with autoDeploy, then list the repository paths that can change the built result:
.towbar/services/web.service.yml
Include shared libraries, lockfiles, build scripts, and Dockerfiles as needed. The Repository’s automation control can pause automatic work during maintenance. A manual Deploy remains a separate action. Start with one manual deployment and verify the running service before enabling automation.

​
Pull request previews

Enable previews for an environment in towbar.yml, then opt the Service in with a base domain:
Eligible pull requests target the branch mapped to staging. Preview secrets are isolated from persistent environment values; datastores do not create previews. Read Preview environments for expiry and cleanup.

​
Other automation

Use notifications to route a Service’s events to additional workspace-configured destinations. It takes effect after a successful environment sync without a deployment. vulnerabilityScanning controls image scanning, while jobs runs scheduled commands from the deployed image. Follow Notifications, Vulnerability scanning, and Scheduled jobs for their separate configuration and execution rules.
Last modified on September 27, 2026