WorkspaceTalon Studio v1.0.2-beta

Workbench

The working area of a workspace: browse the repository, review pending changes and their diffs, and commit them to main or to a change-request branch.

Browsing & working changes

The workbench at /workspaces/<id> (Workspace → Workbench) is where day-to-day editing lands. Its side panel switches between Files (the repository tree), Changes (your pending working changes, each with a side-by-side diff against the branch) and History (commits). The branch you are on is shown, and switched, from the branch menu in the top bar.

Every changed file starts staged, and you unstage the ones you do not want in the next commit. The choice is kept on the server, so it survives reopening the workbench: for files in the working tree it is Git's own index, and unsaved edits from the workbench editor are held as per-branch drafts with their own staged flag. Saving a detection in Forge or Atlas stages its file here rather than committing it.

Stage, commit & branch

On main. Committing writes straight to main, then re-validates the workspace's detections, rebuilds the release package, pushes to your Git mirror if Auto-push is on, and installs to any target set to auto-deploy main. With Require change requests on, only workspace owners can commit to main.

On a branch. New branch… creates a draft change request with its own branch off main and switches you to it. Commits land on that branch and trigger the change request's validation (and AI review, if the review policy runs it automatically). When the branch has at least one commit, Open for review on Workspace → Change Requests moves it from draft to open.

Workspace → Workbench

Committing staged changes. The dialog shows the diff of exactly what will land; write a message and click Commit to <branch>. Unstaged files stay pending as working changes.

Tip

Stage only the files that belong to one logical change before committing. A commit takes an explicit list of paths, so only the files you select land and the rest stay pending, which keeps each change request small and easy to review.