repositories / dotfiles

dotfiles

bugabingas dorkfiles

owned by bugabinga

Review a change

Work in your clone. Each revision gets an annotated tag, review/SERIES/vN. Each reviewer keeps replies in refs/notes/reviews/REVIEWER, attached to the tag object, not the commit.

With Revue

Install Revue to publish a revision, open it in a separate worktree or reply. In this example the series is parser, the revision is v1 and the reviewer is alex. Both message options are optional.

git revue publish parser -m "Handle empty input"
git revue open parser/v1 ../parser-v1
git revue reply parser/v1 --as alex -m "Please test empty input."

With plain Git

Publish. Tag the commit to review and push just that tag. For a revision, use the next version rather than moving an existing tag.

git tag -a review/parser/v1 HEAD -m "Handle empty input"
git push origin refs/tags/review/parser/v1

Open. Fetch the tag and check out its commit in a new worktree.

git fetch origin tag review/parser/v1
git worktree add --detach ../parser-v1 review/parser/v1

Reply. First check for your remote notes ref.

git ls-remote --refs origin refs/notes/reviews/alex

If the lookup succeeds and prints a ref, fetch it into a separate local ref, then merge it into your notes. Resolve any notes conflicts before continuing. If the lookup succeeds with no output, skip this step.

git fetch origin refs/notes/reviews/alex:refs/notes/incoming/alex
git notes --ref=reviews/alex merge refs/notes/incoming/alex

Append to the annotated tag object and push your notes. If the push is rejected because the remote advanced, fetch and merge again before retrying.

git notes --ref=reviews/alex append -m "Please test empty input." 'review/parser/v1^{tag}'
git push origin refs/notes/reviews/alex

Luigit is read-only. Whether a push starts CI depends on the repository’s configured triggers. These instructions do not enforce review or gate merges.