Git & Review
Git & Review, at /git, is a patch queue with CI results, review and approval.
VC-Forge keeps its own git popover, and for one person editing one project that is
right; this is the team-shaped version.
What makes it different from a git client
Section titled “What makes it different from a git client”The patch, the CI run against it, the review, the approval and the merge are five events sharing one subject. So “why did this land” has an answer that survives everybody forgetting, and a machine that was offline while a review happened gets the whole story in order when it pulls - not a status field that has already moved on.
The queue is not stored anywhere. It is folded out of the work band (kinds 2000-2999), exactly the way channels are folded out of the workspace band.
The working copy
Section titled “The working copy”The panel on the right is read live from git on every load, never cached - a cached
branch name is wrong the moment somebody checks something out in a terminal.
MAVEN_REPO_DIR points it at a different repository.
The diff is not on the log
Section titled “The diff is not on the log”It is large, it is already in the repository, and putting it in an append-only file that every machine replicates would multiply the repository across the workspace for no gain. The log records that the patch exists and what was decided; the bytes stay where bytes belong.
How to use it
Section titled “How to use it”- Open a room for the branch in Channels.
- Push a patch; it appears in the queue and as a quiet line in the room.
- Let CI run - or trigger it as a workflow on the patch event.
- Review; approve or reject with a note. Both are signed events.
- Merge. The decision, the approver and the time are on the audit log for good.