The Warrener for developers, stray clones and unsaved work

When it shows#

Only while Castellan's developer features are on: when a developer agent is hired. See Hiring, switching and letting staff go. Off, none of it runs.

Your projects folder#

Where a stray clone moves to: Projects folder in Settings (Advanced), when you set it. Otherwise the folder most of your known clones are in (from Castellan's repositories, and Reeve's list), else the first usual folder that exists (source\repos, Projects, repos, code, GitHub and the like). Every folder your known clones are in counts as a projects folder.

What it finds#

Stray clones: git clones in Downloads, on the Desktop, in Documents, in the temp folder, and at the top of your user folder and OneDrive.

Work not safe anywhere else, in every clone it knows, stray or not, read with plain git that changes nothing and fetches nothing:

• Changed and new files not committed.
• Commits on local branches that no remote has, as of the last fetch.
• Stashes.
• Branches with no upstream, or one that's gone.
• Uncommitted changes in linked worktrees.

Programs running inside a stray clone.

It reads at most 25 clones a round, those never read, or whose git files changed, first. The rest keep what the last round found.

Moving a stray clone home#

Tick it, and press Move the ticked clones. It asks first. The clone is checked again, and the move is refused when:

• Castellan or the Steward lists it where it is;
• a program is running inside it;
• it has linked worktrees, which a move would cut off;
• git can't read it;
• the projects folder is on another drive (that would be a copy and a delete, which the Warrener never does);
• it gained uncommitted changes since you ticked it.

A move is one rename of the whole folder into the projects folder (as name-2 when the name is taken), uncommitted changes and all. Put back renames it back if its old place is free. Nothing is ever deleted.