Path owners and protection
Path owners
A .lodeowners file at the root of the repo says who owns which folders, like CODEOWNERS. The last matching line wins:
Content/Characters/** group:char-art
Source/** group:programmers @lead
Content/Sandbox/** # no owners: anyone
.lodeowners role:admin # default: role:maintainer
.lodebase/** role:maintainer # pipelines (the default)Owners are group:<name> (a group from your sign-in provider), @user, or role:<role>.
Owners change their paths freely. Anyone else's submit that touches owned paths is refused, naming the owners; they open a merge request instead, and an owner approves it. Nothing is hidden: owners only gate who can land changes without review. The file is always read from the target branch, so a change can't loosen the rules that judge it.
sh
lode owners # who owns your local changes
lode owners Content/Characters/ # or any pathsBranch protection
Admins set rules per branch pattern; the most specific pattern wins. Rules live on the server and every change to them is in the audit log.
sh
lode protect set main --approvals 1 # merge requests only, maintainers merge
lode protect set 'release/*' --approvals 2 --merge-role admin
lode protect set 'dev/*' --allow-submit --approvals 0 --merge-role contributor --no-owners
lode protect set main --check Build --merge-queue # a pipeline must pass, via the queue
lode protect # list
lode protect remove 'dev/*'| Option | Meaning |
|---|---|
--allow-submit | Direct submits are allowed (otherwise changes go through merge requests) |
--approvals N | Approvals a merge request needs |
--merge-role | Minimum role to merge (default maintainer) |
--no-owners | Don't require .lodeowners approvals |
--keep-approvals | Keep approvals when a new revision arrives |
--check NAME | A pipeline that must pass on the merge request (repeatable) |
--merge-queue | Merge through a queue that re-runs the checks on the latest head first |
Unprotected branches take direct submits, still enforce path owners, and only their creator or a maintainer can delete them. Admins can push past approvals or owners with --bypass "reason"; that lands in lode audit with the reason. Nothing bypasses conflicts.