prreviewbuddy 0.53.1 → 0.55.1
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 +61 -0
- package/dist/{delete_review-DMJXD3bf.js → delete_review-B2bqhgtx.js} +383 -34
- package/dist/main.js +1 -1
- package/dist/server.js +211 -10
- package/package.json +1 -1
- package/static/chunk-BeqgAIrQ.js +4 -4
- package/static/chunk-BpiqRF0Y.js +1 -0
- package/static/chunk-RriGSD6H.js +1 -0
- package/static/notifications.js +1 -1
- package/static/reviews.js +1 -1
- package/static/shell.css +2 -0
- package/static/sidebar.css +137 -0
- package/static/workspace.js +36 -36
- package/static/chunk-CofqJ-Qn.js +0 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,66 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.55.1
|
|
4
|
+
|
|
5
|
+
**Load more on the Notifications page.** The list shows the newest fifteen, and Load more reveals
|
|
6
|
+
fifteen more at a time, the same way each section of the Reviews page does. Mark all read still
|
|
7
|
+
covers every notification, including the ones not yet shown.
|
|
8
|
+
|
|
9
|
+
## 0.55.0
|
|
10
|
+
|
|
11
|
+
Published with 0.54.0, which did not go to npm on its own: read both entries below.
|
|
12
|
+
|
|
13
|
+
**Why this change?** The Overview now says why the change exists, between Author's context and
|
|
14
|
+
What's changing, and how it knows:
|
|
15
|
+
|
|
16
|
+
- **Stated by the author**, with a short quote from the description. The quote is checked
|
|
17
|
+
against the description the analysis read, and **From Author's context** takes you to it.
|
|
18
|
+
- **Likely motivation**, when nothing states it but the change gives evidence: a test, an issue,
|
|
19
|
+
a commit message. The evidence is listed, with links to its files.
|
|
20
|
+
- **Motivation unclear**, when knowing why would change how the change should be read. The
|
|
21
|
+
analysis asks the author one question, filed first on the Questions page under **Intent**, with
|
|
22
|
+
the same Mark answered control as every other question.
|
|
23
|
+
|
|
24
|
+
Nothing is shown when the reason would not change the review, or for analyses made before this
|
|
25
|
+
version. A claim that fails its check is never shown in the model's words: an unverified quote or
|
|
26
|
+
an inference without evidence becomes "unclear" with a neutral sentence when the analysis asked a
|
|
27
|
+
question, and is left out when it did not. The workspace says so under **What the harness
|
|
28
|
+
corrected**.
|
|
29
|
+
|
|
30
|
+
- The workspace's prompt now reads the pull request's description. A local branch's commit
|
|
31
|
+
subjects are labelled as commits rather than as a description.
|
|
32
|
+
- Updating an analysis with new commits keeps its motivation, since commits show what changed
|
|
33
|
+
rather than why. The extension 0.25.0 shows the same Overview.
|
|
34
|
+
- Once the Intent question is marked answered, the Overview says **Motivation was unclear when
|
|
35
|
+
analysed** and offers **Run review again**, since marking a question answered records no answer
|
|
36
|
+
for an update to use. A new analysis reads the description and conversation as they now stand.
|
|
37
|
+
The workspace page can now start that analysis itself, as `review --reanalyse` does.
|
|
38
|
+
- Evidence follows one rule in both places. A changed file opens in the diff, and a real unchanged
|
|
39
|
+
file opens in the source view. A path the reviewed commit does not hold is removed and listed
|
|
40
|
+
under **What the harness corrected**. A path that cannot be checked, which is any path outside
|
|
41
|
+
the pull request in the extension, is shown as an unverified path rather than a link.
|
|
42
|
+
- A quote counts as the author's only if it is in the text they wrote. A partly filled template's
|
|
43
|
+
comments, unticked checklist items and bare headings no longer count.
|
|
44
|
+
- Tabbing into a closed Author's context preview opens it, so a focused link or Copy button is
|
|
45
|
+
never hidden under the fade.
|
|
46
|
+
|
|
47
|
+
## 0.54.0
|
|
48
|
+
|
|
49
|
+
**The Overview starts with the change, then gives the verdict.** The risk card used to come first,
|
|
50
|
+
and its takeaway read like the pull request's description. The Overview now opens with
|
|
51
|
+
**Author's context**, the pull request's description exactly as the author wrote it. Under it is
|
|
52
|
+
**What's changing**, the analysis's summary of what the code does. The risk card, the counts and
|
|
53
|
+
the suggested review path follow, as before.
|
|
54
|
+
|
|
55
|
+
- Author's context appears only when the pull request has a description. A description that is
|
|
56
|
+
only an unfilled template counts as none, and so does a review of a local branch or commit.
|
|
57
|
+
- Each analysis keeps the description it was made against. If the author edits it later, older
|
|
58
|
+
analyses still show what they read, and the next analysis reads the new text.
|
|
59
|
+
- Long descriptions open as a preview with **Show full description**. All of it, checklists and
|
|
60
|
+
testing notes included, is one click away, and **Show less** folds it again.
|
|
61
|
+
- The workspace now fetches the description in the same `gh pr view` call it already made. The
|
|
62
|
+
extension 0.24.0 shows the same Overview.
|
|
63
|
+
|
|
3
64
|
## 0.53.1
|
|
4
65
|
|
|
5
66
|
**The running KISS review has its normal layout back.** While a KISS review ran, its progress
|