Make your next change

Begin by seeing where you are

Open a terminal inside your existing Lore working tree. Check which branch you are on and whether there are local changes before taking the next step.

lore status --scan

When you need the latest shared work, use lore sync. Check your local changes first; sync can require conflict resolution.

Make one understandable change

Edit and save your files. Stage only the paths you intend to include, inspect the result, and write a commit message that explains the change.

lore stage README.md
lore status --scan
lore commit "Explain how to open the world"
lore push

Staging marks paths for the next commit. If you edit a staged file again, the commit uses the file as it exists when you commit. Recheck your work before recording it.

Keep experiments on a branch

A branch gives an experiment its own line of revisions. Check the branch reported by status after creating or switching branches.

lore branch create lighting-study
lore status --scan

To move to an existing branch, use lore branch switch main. Resolve or save local work before switching. Use the official quickstart for a complete branching and merging exercise.

When sharing needs a second look

Push reports divergence? Another contributor may have shared work first. Sync, inspect the resulting changes, resolve any conflicts, then commit and push as appropriate. Avoid destructive “reset everything” fixes.

A binary asset conflicts? Agree with your teammate which result to keep. A scene or texture often needs a human decision rather than a text merge.

Something is unclear? Start with lore --help or lore branch --help, then follow the reference for your installed release.