Skip to content
Sarj Repo Standards
core/migration/batch-too-large

Move one component at a time

One selected Git tree declares at most one component relocation.

warning beta

Examples

FlaggedFails
schema_version = 1
repository_id = "example-repository"
policy = "example"
policy_version = 1


[[components]]
id = "api"
kind = "service"
path = "applications/alpha/api"
owner = "@example/alpha"


[[components]]
id = "worker"
kind = "worker"
path = "applications/alpha/worker"
owner = "@example/alpha"


[[migration_paths]]
component_id = "api"
from = "apps/api"
to = "applications/alpha/api"


[[migration_paths]]
component_id = "worker"
from = "apps/worker"
to = "applications/alpha/worker"
PassesClean
schema_version = 1
repository_id = "example-repository"
policy = "example"
policy_version = 1


[[components]]
id = "api"
kind = "service"
path = "applications/alpha/api"
owner = "@example/alpha"


[[migration_paths]]
component_id = "api"
from = "apps/api"
to = "applications/alpha/api"

Why it matters

Independent moves share one review and rollback boundary, so one failed move can force all verified moves to be reverted together.

How detection works

Reports when the selected manifest contains more than one migration path entry.

What is inspected

  • Migration path entries from the exact selected manifest.

Limits

  • Prohibiting a separately reviewed sequence of component moves.

How to fix it

Split the migration into independently reversible component moves.

  1. Keep one migration path entry in the selected tree.
  2. Verify and merge that move before declaring the next relocation.

Verify

  • Run repo-lint check and confirm one migration path remains.