Task folders and review

By default, a task taken from the board gets its own folder and Git branch. This lets several tools work on one repository without sharing a working tree.

How task folders work

For a repository named example-app, a task gets a folder beside the project under example-app-seggo/ and a branch beginning with seggo/. The exact folder and branch appear on the task.

Seggo creates them from the project’s current branch. If the matching worktree or branch already exists and belongs to this task, Seggo reuses it. If Git is unavailable or the project is not a repository, the task can still be claimed and the app explains why it will use the project folder.

Keep Give each task its own folder on when tools may edit the same codebase at once. A tool must work in the folder Seggo returns. It should not invent another folder or branch.

Review finished work

When Finished work needs review is on, completed tasks wait in Needs review. Open a task to see its summary, changed files, latest checkpoint and history. You can:

• approve the task;
• request changes with a note;
• ask another tool to review it.

Another tool may comment, approve or request changes. It cannot review its own work. Its approval may still wait for your confirmation, depending on Project settings.

The Ready to merge page

Open a project and choose Ready to merge. It’s a list with one row per task branch, in three groups:

• Ready to merge (N): branches with commits that aren’t in main yet. Each row shows the task, how many commits and files it adds, and whether it merges cleanly. Choose Merge into main to bring that task’s work back. The row’s ⋯ menu has Remove its folder… if you want to drop the task folder.
• No commits yet (N): task folders where no tool has committed anything yet. There’s nothing to merge.
• Already merged (N): branches whose work is already in main. This group is collapsed. Each row has Remove folder….

A successful merge marks the task Done and can unblock tasks that depend on it. If a branch conflicts with main, Seggo doesn’t merge it. Resolve the conflict in that task’s folder, commit, and come back.

Clean up merged folders

Task folders stay on your computer after their work is merged. In Already merged, choose Clean up merged folders… to tidy them away.

Before anything happens, Seggo shows exactly which folders it will remove and which it will keep. It only removes a folder when its branch is fully merged into main and the folder has nothing uncommitted. It never deletes unmerged work and never forces a removal. Each cleanup is logged in What Seggo changed.

Merging is always your call

Seggo never pushes. Merging happens only when you click Merge into main, even when tools may mark tasks Done or review one another. When you’re ready to share the work, push main yourself.