A task on a repository whose mesh is enabled works on the mesh
When the repository declares its mesh enabled, an active task's scope is claimed on the mesh — `start` brings the checkout's shared server up and claims it, `check` and `finish` claim it again when a server answers — and a task completed without that claim is refused.
blocking A violation stops the command with exit 10.
The chain
A rule is enforced only when every link below holds. majordomus doctor resolves each one from the source on every run; this page shows what it resolved.
- 1 Declared majordomus.task-on-the-mesh
- 2 Validator mj_validate_task_on_the_mesh
- 3 Runs under check, finish
- 4 On violation exit 10
- 5 Proved by test/cases/3068_a_task_off_the_mesh_is_refused.sh
- 6 Run by CI .github/workflows/validate.yml
Where it runs
- majordomus checkIs the current task still consistent with its policy, its scope and this checkout?
- majordomus finishEvaluate the finish contract and refuse the outcome if any line of it is unmet.
Read it here
majordomus doctrine show majordomus.task-on-the-mesh
majordomus check --rule majordomus.task-on-the-mesh