Reference
Reading a verdict
Every field in land's answer, every reason a branch is refused, and the exit codes.
An example
$ land merge sub/api sub/ledger --onto main --json { "landed": ["sub/api"], "refused": [{ "who": "sub/ledger", "why": "tests_failed", "failing": [{ "test": "tests/test_ledger.py::test_reverse", "assert": "assert 110 == 90" }], "repro": { "commit": "071366837c", "run": "python -m pytest tests/test_ledger.py::test_reverse" }, "hitBy": "sub/api" }], "guarding": "3/3", "removed_tests": [], "newly_skipped": [], "tests_changed": [], "local": { "push": "git push --atomic origin 8364fb3…:refs/heads/main refs/land/attestations" } }
Fields
- landed
- The branches that are in the result.
- refused
- The branches that are not, each with who, why and what to do. For a test failure: failing (the test and its assertion), hitBy (the branch it clashes with) and repro (a commit and a command that reproduce it).
- guarding
- How many of the tests on main pass and so can catch a regression, such as 409/412.
- removed_tests, newly_skipped, tests_changed
- Any test a branch deleted, skipped or edited. Always shown, so an agent can't weaken tests quietly.
- result
- The merge commit land built in your repository, with your origin/main and each landed branch as parents.
- local.push
- The exact command that pushes the result and land's signature. Run it as printed.
Reasons for a refusal
Every value of why, and what the agent does next.
| why | what your agent does |
|---|---|
| tests_failed | Fix the code those tests use (hitBy names the other branch it clashes with), run land merge again |
| conflict | Rewrite your version of the named entity on top of the one that landed, run land merge again |
| collection | Tests could not load (an import or syntax error). Fix it, run land merge again |
| dependencies | The new dependencies would not install. Fix the dependency files, or add the tool to .land/setup.sh, run land merge again |
| policy | The change edits protected tests. Revert those edits |
| env, timeout, oom | The run failed, not your code. Run land merge again |
| no_plan | Nothing was checked. Pick a plan on your dashboard, then run land merge again |
| "dirty" | Commit the subagent's work in that worktree, merge again |
| "state": "running" | Run the same land merge again to wait for the result |
| exit code 4 | land could not check this run (its side, not your change). Run land merge again |
Exit codes
- 0
- Every branch landed. Run the printed local.push.
- 1
- Some branch was refused. The rest landed and can be pushed.
- 2
- A usage or local problem. The JSON has error and the exact fix command.
- 3
- Still running. Run the same command again to wait, it never starts the merge twice.
- 4
- land could not check this run, a problem on its side. Nothing to push. Run it again, and tell us if it repeats.