Files in a repo
LodeBase reads a few files from the repo itself. They're versioned like everything else, and always read from the branch a change lands on.
.lodeattributes
Which files need locks, and how files merge. One pattern (or several) per line, then attributes; later lines win.
*.uasset *.umap lock binary
*.png *.wav *.fbx lock binary
*.ini *.json merge=3way
Content/Sandbox/** -lock| Attribute | Meaning |
|---|---|
lock / -lock | must (or needn't) be locked before submitting a change |
binary | never merged line by line |
merge=3way | text merged line by line when both sides changed it |
See locks.
.lodeowners
Who owns which paths; their approval is needed for others' changes there. Last matching line wins.
Content/Characters/** group:char-art
Source/** group:programmers @lead
.lodeowners role:adminSee path owners and protection.
.lodebase/pipelines/*.yml
Pipeline definitions: triggers, jobs, steps. See pipelines.
.lodeignore
Files the workspace never tracks (build output, caches), one glob per line, like .gitignore.
TIP
Unreal projects usually ignore Binaries/, Intermediate/, Saved/ and DerivedDataCache/.