prreviewbuddy 0.36.10 → 0.42.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,145 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.42.0
4
+
5
+ **A review page no longer says "Review up to date" when it isn't.** The status beside **Check for
6
+ updates** used to be worked out once, when the page opened. It now checks again on its own when you
7
+ come back to the tab and once a minute while you're looking at it, so a commit to the branch you're
8
+ reviewing shows as **Code changed** without pressing anything. These checks never contact GitHub and
9
+ are silent: nothing flashes, and a warning you dismissed stays dismissed until something newer
10
+ arrives.
11
+
12
+ **Pull request pushes show on the page, not just in notifications.** The workspace server already
13
+ checked your pull requests on GitHub every few minutes and told you when one moved. The page itself
14
+ could only see commits your repository had fetched, so it could say "up to date", and **Check for
15
+ updates** could say **No change**, right after a **PR updated** notification. The page now shows
16
+ **PR updated** as soon as the server has seen the push, with **Update review** beside it, whether or
17
+ not anything has been fetched. The server watches the pull requests of reviews that are queued,
18
+ saved, or not yet marked reviewed, so those are the ones this applies to. Once **Update review** finishes, the page and the card on the
19
+ Reviews page stop saying the pull request moved straight away; an unread **PR updated** notification
20
+ clears at the next check a few minutes later, as before. If the author pushes again while the update
21
+ is running, the page says so rather than hiding the newer push.
22
+
23
+ ## 0.41.0
24
+
25
+ **Your place is kept when a page reloads itself.** The Reviews page reloads whenever something on it
26
+ changes, such as a review finishing or the review queue changing in another tab, and a review
27
+ reloads when its analysis produces something new. Both used to jump back to the top. They now come
28
+ back where you were. Opening a page from a link still starts at the top, and each view of a review
29
+ and each filter of the list keeps its own place.
30
+
31
+ **Add a selection to the review queue.** In selection mode, the bar has **Add to review queue**,
32
+ which adds every ticked review in the order the list shows them. Reviews already queued keep their
33
+ place. The queue holds fifty reviews; anything that does not fit stays ticked, and the bar says why.
34
+ Reviews deleted since they were queued no longer take up any of those fifty places.
35
+
36
+ **Save a review from its own page.** The review page's **...** menu has **Save review**, which does
37
+ what the star on the Reviews page does. When the review is saved it reads **Remove from saved**.
38
+
39
+ **Copy an issue or a question, ready to post.** Every issue and question has a **Copy** button that
40
+ puts it on the clipboard as Markdown. An issue copies its title in bold, its description, then the
41
+ file and line. A question copies the question in bold, why it matters, then the file. Both list any
42
+ unchanged files they rely on. The severity, confidence and theme labels are left out, so it pastes
43
+ straight into a pull request comment.
44
+
45
+ ## 0.40.0
46
+
47
+ **See which reviewed pull requests have merged.** The workspace server's regular pull request check
48
+ now also reads whether each pull request is open, merged or closed, from GitHub, in the same request
49
+ it already made. A card whose pull request has merged says **Merged** beside its status, and one
50
+ closed without merging says **PR closed**. Neither changes the review's own status: a review stays
51
+ **In progress** until you mark it reviewed, and a reviewed card keeps its **Merged** badge. When a
52
+ pull request you are watching merges or closes you get one notification, **PR merged** or **PR
53
+ closed**, and never a repeat. Pull requests that had already merged before this version are marked
54
+ quietly, without a notification each. A merged pull request is not checked again.
55
+
56
+ **A PR filter on the Reviews page.** Beside **Status**, **PR** narrows the list to pull requests that
57
+ are **Open**, **Merged** or **Closed**. It combines with Status, so **In progress** with **Merged**
58
+ lists the merged reviews you have not finished. Reviews with no pull request only appear under
59
+ **Any**.
60
+
61
+ **Select all in selection mode.** The bar at the bottom has **Select all**, which ticks every review
62
+ the search and filters are showing, on every page. To clear out merged reviews: set PR to Merged,
63
+ press Select, **Select all**, then **Mark reviewed**.
64
+
65
+ ## 0.39.3
66
+
67
+ **Reviews of a branch now notice when the branch moves, not only reviews of a pull request.** The
68
+ workspace server already checked the pull requests behind your queued, saved and in-progress reviews
69
+ every few minutes. It now checks reviews with no pull request too, by looking at the branch they
70
+ follow in your own repository, with no network access. When you commit to that branch, the review's
71
+ card says **Branch updated** and you get a notification, the same way a moved pull request says
72
+ **PR updated**. The card and the review page's **Check for updates** use the same check, so they
73
+ always agree.
74
+
75
+ **Fetch updates on the Reviews page.** A review that follows a remote branch, such as
76
+ `origin/feature`, only moves when your repository fetches. **Fetch updates** fetches each repository
77
+ once and then checks those reviews straight away, so a teammate's push shows up without opening each
78
+ review. It covers the reviews the page is showing after search and filters. In selection mode,
79
+ **Fetch selected** in the bar at the bottom covers only the reviews you ticked. Nothing is fetched
80
+ unless you press one of them, reviews of a local branch are never fetched for (a fetch cannot move
81
+ them), and your branches, checkout and working tree are never changed. If one repository cannot be
82
+ reached the others still fetch, and the button says so: **Fetched 2 of 3 repositories**. Branches
83
+ your fetch configuration excludes are left out rather than reported as fetched.
84
+
85
+ **A tidier Reviews toolbar.** The five status buttons are now one **Status** menu, with the same
86
+ choices and the queue count as **Queue (4)**, so search, filters and Fetch updates fit on one row.
87
+
88
+ ## 0.38.8
89
+
90
+ **Update review replaces the review instead of running on top of it.** While an update runs, the
91
+ middle of the page shows its progress in place of the findings that are about to be replaced. The
92
+ sidebar is dimmed, and Buddy AI keeps its conversation but waits until the new review is ready. The
93
+ page no longer flashes while an update runs: on reviews without a connected pull request it was
94
+ reloading itself every second. When the update finishes the page switches to the new review once. If
95
+ it fails, the previous review comes back unchanged with the reason.
96
+
97
+ **Nothing you do during an update is lost any more.** Questions ticked, findings dismissed and Buddy
98
+ AI answers given while an update was running could be overwritten when it finished. They are now kept,
99
+ including when the update runs from the terminal and you are working in the browser at the same time.
100
+
101
+ **The review header separates status from action.** "Review up to date" is now plain status, with a
102
+ **Check for updates** button beside it. A check that finds new commits brings back a Code changed
103
+ banner you had dismissed.
104
+
105
+ **The "does not read pull request conversation" note can be dismissed.** Dismissing it hides it for
106
+ that host. The reason stays on the PR context page.
107
+
108
+ **Update results are easier to scan:** **Review updated · 7bc233f · 2 issues fixed · 1 new issue ·
109
+ 2 questions answered**.
110
+
111
+ ## 0.38.2
112
+
113
+ Two gaps in the per-investigation summary added above: a finding revised a second time was left out
114
+ of the count, so a run that regraded something could report "no findings changed"; and findings an
115
+ earlier investigation had added were counted again by every investigation that followed.
116
+
117
+ ## 0.38.1
118
+
119
+ A second repository investigation could undo the first one's conclusions. Findings an earlier
120
+ investigation had confirmed or refuted went back to plain "Investigated" whenever the new evidence
121
+ had nothing to say about them, while the sentence explaining the original conclusion stayed on the
122
+ card beneath it. A conclusion now survives an investigation that does not bear on it, and only
123
+ evidence that positively changes it can replace it. Each investigation's summary counts what that
124
+ investigation moved, rather than everything concluded so far.
125
+
126
+ ## 0.38.0
127
+
128
+ **PR Review Buddy notices when a reviewed pull request moves.** The workspace server checks the
129
+ pull requests behind your queued, saved and in-progress reviews every few minutes, using the `gh`
130
+ you are already signed in to, and records one notification when a request gains commits: **PR
131
+ updated - 3 new commits**, linking to the review, where **Update review** is still yours to press.
132
+ Nothing is re-analysed for you, nothing is reordered, and nothing about the review changes. Reviews
133
+ of a local branch or a single commit are not watched, because there is no pull request to watch.
134
+
135
+ Also fixed, and older than the above: **updating a review could reopen findings and questions an
136
+ earlier update had already settled.** Each update judged the whole list against only the newest
137
+ commits and was never told what the previous update had concluded, so a fix or an answer from two
138
+ commits ago read as "these changes do not address it". Verdicts now travel forward, a resolved
139
+ finding stays resolved, and an answered question keeps its answer - including on reviews already
140
+ left in that state, whose answers are recovered on their next update.
141
+
142
+
3
143
  ## 0.36.10
4
144
 
5
145
  **Syntax highlighting in the file viewer.** Code opened in the review is now coloured by language: