Skip to content

v0.11.0 — .review stays out of the review

Latest

Choose a tag to compare

@codywilliamson codywilliamson released this 17 Aug 06:00

loupe's own .review file no longer turns up inside the review, and hiding it no longer edits a tracked file. Closes #5.

Only the untracked listing in working-tree mode ever filtered .review. A .review that had been committed to the repo before you first ran loupe sailed straight through branch, range, staged and browse listings as an ordinary reviewable file — a diff of your own review notes, sitting in the middle of the code you were trying to read.

Added

  • Settings menu — a gear in the top bar, holding one setting: Review the .review file. Settings live in ~/.loupe/state.json, so they stick across launches even though each one picks a fresh port.

Changed

  • .review stays out of the review — one filter now covers every mode, applied to the launch diff and every refresh. Turn the new setting on to review it like any other file.
  • .review is excluded via .git/info/exclude, not .gitignore.gitignore is tracked, so appending to it created a working-tree change that surfaced in the very review you were running. The exclude file is per-clone and never committed, and loupe writes it whether or not a .gitignore exists (it skips the write entirely when .gitignore already covers .review). Existing .gitignore entries are left alone.

Nothing to do on upgrade. If a previous loupe added .review to your .gitignore, that entry still works and is left untouched.