Skip to content
Odyn

Daily workflow

Once you have dependencies in deps/ and pinned in Odyn.lock, these are the commands you reach for day to day.

Restore on a fresh checkout

Section titled “Restore on a fresh checkout”
Terminal window
odyn sync

Restores every dependency in Odyn.lock to its pinned commit. Run this on a fresh clone, or whenever deps/ has drifted. Use --skip <name> to skip a dependency, or -f to hard-reset local changes.

Check for drift

Section titled “Check for drift”
Terminal window
odyn status

Reports dependencies that are missing, modified, or on a different commit than the lockfile expects. Exits non-zero if anything is off, which makes it useful in CI.

Update a dependency

Section titled “Update a dependency”
Terminal window
odyn update <name>

Re-pin a dependency to its latest commit. You can also pin to a tag, a branch, or a specific commit:

Terminal window
odyn update mydep -t latest
odyn update mydep -t v2.0.0
odyn update mydep -b main
odyn update mydep abc123def

When tracking a branch with -b, the branch name is recorded in Odyn.lock so future updates can follow it.

Remove a dependency

Section titled “Remove a dependency”
Terminal window
odyn remove <name>

Deletes the dependency’s folder under deps/ and removes its entry from the lockfile.

Commit the lockfile

Section titled “Commit the lockfile”

Odyn.lock is the source of truth. Commit it to version control. It is better to not commit deps/ directly, but you can if a dependency becomes inaccessible.

What’s next

Section titled “What’s next”

Browse packages with search and lists, or see the full command reference.