Get started
Concepts
The few words land uses, and what each one is in terms you already know.
Terms
- Branch and target
- Each agent's finished work is a committed branch. The target is where it goes, usually main. land merges onto your own origin copy of the target, so fetch before you merge.
- Merge by entity
- land merges by function, class and method instead of by line. Two agents editing different functions in the same file combine cleanly. Two agents changing the same function in different ways is a conflict, and land never picks a winner.
- Test command
- A command you name with --test, such as python -m pytest -q. land runs exactly that. You can name several, and each is checked and reported on its own.
- Environment
- What
.land/setup.shleaves behind on a plain Debian machine. It is built once and reused, so a check starts in about a second. - Check
- One run of your test commands on the merged result, offline, in a small virtual machine of its own. One check covers every branch in the call.
- Read set
- Every file a test command read during its last run. When none of them changed, land reuses the earlier result instead of running the command again.
- Verdict
- The JSON land prints: which branches landed, which were refused and why, and the command that pushes the result.
- Attestation
- land's signed statement that one exact tree passed. It travels with the commit in
refs/land/attestations, and anyone can check it offline withland verify.
If you know CI
How land's pieces line up with the CI words you already use.
- A merge queue entry
- A branch in a land merge call. land combines all of them and tests them together, instead of one at a time.
- A required CI job
- A test command. Each named command is checked on its own and can refuse a branch.
- A CI runner image
- The environment built from .land/setup.sh.
- Test caching
- Reusing a command's result when nothing in its read set changed.
- A green status check
- An attestation, except anyone can verify it offline and it covers the exact files.