Automatic deployments

Coolify can start a deployment when a Git provider reports a repository change or when an external workflow sends an authenticated deployment request.

Choose the trigger that matches how the application source is connected:

Use this method when the application was created by selecting a repository through a GitHub App or GitLab source integration.

The integration receives provider events for Coolify, so you do not need to copy a manual Git webhook URL.

Enable automatic deployments

Open the application, select Configuration > Advanced > Deployment & Git, then enable Auto Deploy.

Push to the configured branch

Push a commit to the branch selected for the application. A push to another branch does not update the production application unless that branch is configured for a preview or another application.

Verify the deployment

Open Deployments and confirm a webhook deployment appears for the pushed commit.

If no deployment appears, inspect the provider integration and confirm the application still has access to the repository.

Limit deployments by changed paths

Use Watch Paths under Configuration > General > Build when a monorepo should deploy only after matching files change.

Patterns are evaluated in order and support *, **, ?, and negation with !. The last matching pattern wins.

For example:

apps/api/**
packages/shared/**
!apps/api/**/*.md

Watch paths filter Git provider webhook events that include changed-file information. They do not block deployments started manually from the dashboard or through the authenticated Deploy Webhook.

Test the patterns with a documentation-only commit before relying on them for production automation.

Disable automatic Git deployments

Turn off Configuration > Advanced > Deployment & Git > Auto Deploy to keep the source connection while ignoring automatic commit deployments from Git provider events.

You can still select Deploy or Redeploy, or call the authenticated Deploy Webhook from an external workflow.