Skip to content
Sarj Repo Standards
core/migration/target-missing

Commit files at the migration target

Every declared migration target contains at least one tracked file.

warning beta

Examples

FlaggedFails
README.md
PassesClean
applications/alpha/api/pyproject.toml

Why it matters

The manifest can claim a completed move while ownership and checks point to a path that does not exist.

How detection works

Reports when the selected Git tree has no tracked file at or below a migration's declared target path.

What is inspected

  • Tracked paths from the exact selected Git tree.

Limits

  • Checking untracked worktree files.
  • Executing repository build commands.

How to fix it

Commit the component files at the declared migration target.

  1. Move and add the component's files at the declared target path.
  2. Update path-sensitive build and workspace configuration in the same change.

Verify

  • Run repo-lint check against the resulting commit.