On your computer
Everything Orchestra keeps is under.orchestra in your home folder (on
Windows, your user profile).
The desktop app, the terminal client and your agents all read the same store,
through the Local daemon that runs in the background.
In git
What you share goes to git, underrefs/orchestra/, with one ref per person
for each kind of work:
Each person only ever writes their own refs, and every write is a new commit
on top of the last, so nothing anyone shared is overwritten or merged.
Why refs, not branches
Refs outsiderefs/heads/ stay out of everyone’s way: they do not show up as
branches, git clone and git pull do not fetch them, CI does not run on
them, and branch protection on main does not apply to them. Your teammates’
checkouts stay exactly as they were. Orchestra fetches only the refs it needs,
and from them only the memories and sessions a task needs.
Look for yourself
List what a repository holds with plain git, without Orchestra:orchestra memory export --out <folder> writes one Markdown file per memory.
Many repositories in one folder
If your team keeps several repositories side by side (for example~/code/acme/api, ~/code/acme/web and a dozen more), run
orchestra enable --local in the parent folder. It turns on every
repository in it. A session you start in the folder and that works in two of
them is published to each repository it touched, and each memory goes to the
repository its evidence came from. See
A folder of repositories.
Protected branches and hosts that refuse refs
Protectingmain, or requiring pull requests, does not affect Orchestra:
nothing is ever pushed to a branch. On GitHub, branch and tag rulesets apply
to branches and tags only.
Some organizations allow only branches and tags at all (a GitHub push
ruleset, or a server hook). Then the host refuses refs/orchestra/*. Two
things tell you: orchestra doctor pushes a small test ref to each
repository (and deletes it at once) and says when it was refused, and
orchestra share log shows the refused push with the host’s own words. Either
ask for refs/orchestra/memory/*, refs/orchestra/sessions/* and
refs/orchestra/issues/* to be allowed, or use a memory repo.
A memory repo for the whole team
A team admin can send everything to one dedicated repository instead of each code repository:orchestra/memory/<person>,
orchestra/sessions/<person> and orchestra/issues/<person>. Anyone who can
read the memory repo reads work from every repository in the team, so keep it
private to the team. See A memory repo.
What teammates see, and when
Visibility follows your git host: whoever can read the repository (or the
memory repo) can read what was shared there, and nobody else.
Related
- Working as a team on Local: start or join a team, step by step
- Troubleshooting Orchestra Local: what each problem looks like and how to fix it
- Shared memory: sharing, the team key, publishing and unpublishing in detail