Skip to main content
A repository with several services should not rebuild all of them on every push. Detection lists the workspace packages in a connected repository, and each package carries a ready-made set of watch paths so a push only redeploys the services it touches.

​
What detection finds

Detection reads the provider’s file tree (no clone on GitHub, GitLab and Gitea) and recognises: A directory counts as a package when it matches a workspace glob and holds a package.json, go.mod or project.json. Up to 60 packages are listed.

​
Watch paths per package

Each package gets a deploy filter made of:
  • its own directory (services/web/**),
  • the directory of every workspace package it depends on (read from dependencies and devDependencies in its package.json),
  • the root files that change every install or build: lockfiles, package.json, pnpm-workspace.yaml, turbo.json, nx.json, tsconfig.base.json, go.work, go.mod and go.sum.
So a change under services/api skips the web service, a change under a shared package redeploys only its dependents, and a root lockfile change redeploys everything. The filter is the same doublestar deploy_paths list described in Git integrations; an empty diff never matches.

​
From the dashboard

Open the app’s Source tab, edit the build settings, and look under Workspace packages. Use this package sets the package directory as the build root (with its Dockerfile when it has one) and saves its watch paths. To run several services from one repository, connect the same repository to one app per package and apply a different package to each. The same panel can dry-run a change: paste changed file paths, one per line (list both names of a renamed file), and each package shows Redeploys or Skipped, together with the verdict for this app.

​
From the CLI

--package applies the build root and watch paths in one step. affected is read only.

​
API

POST /api/v1/apps/{name}/git-source/detect returns a packages array (name, dir, tool, dockerfile, depends_on, watch_paths). POST /api/v1/apps/{name}/git-source/affected takes { "files": [...] } and returns whether this app deploys and which packages are affected.

​
Try it

test/fixtures/monorepo is a pnpm workspace with two tiny services and a Dockerfile each.

​
One app per package

In the New app wizard, a monorepo lists its packages. Select several and press Create an app for each selected package: each app gets the package directory as its build root and its watch paths. levelrail-cli apps analyze REPO_URL lists the packages too. See Import a repository.

​
Limits

  • Dependencies are followed for Node packages only; Go modules are matched by directory and root files.
  • Watch paths are saved on the app when you apply a package, so editing the workspace later means applying the package again.
  • Push events whose changed-file list the provider does not return deploy unfiltered.
Last modified on October 17, 2026