Skip to content

v0.3.0 — Adjust findings before publishing

Choose a tag to compare

View all tags
@WTLAIB WTLAIB released this 25 Oct 21:09
· 27 commits to main since this release
v0.3.0
6dcb4d2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Azure DevOps PR Review for OpenCode — 0.3.0

AI reviews. You decide what gets posted. This release lets you exclude findings
or change their severity after reading a comment preview. AZPR prepares a new
preview without rerunning the review, while keeping the original findings and
report intact.

Try it after a preview

Use your review ID and finding IDs from its report:

/pr-comment <review-id> --exclude F-1 --severity F-2=low

F-1 is excluded from the new preview; F-2 appears as low in the summary, with no
new inline comment. Comment planning uses a model again, so other wording may
change. Read the whole new preview, then publish from the same conversation:

/pr-comment <review-id> --publish

What changed

  • Choose the findings and severity. --exclude and --severity each
    replace their own saved list; none empties that list. For example,
    --exclude F-1 followed by --exclude F-2 excludes only F-2. Name both to
    keep both out. --reset clears both lists and plans again. A changed
    severity changes publication, not the evidence or verification of a finding.
    Excluding every finding plans and posts nothing (NOTHING_TO_POST).
  • Reopen the saved preview. /pr-comment [review-id] --show displays it
    without a model or Azure DevOps request. It includes the saved adjustments.
  • Read the new preview before publishing. An adjusted review, including
    one reset since, needs a saved preview planned after its latest adjustment.
    Adjustments are saved together with dropping the earlier preview; a failed
    save changes nothing. A new preview whose save fails is dropped. After a
    stop or restart during planning, prepare a new preview before publishing.
    Once publication starts, the review cannot be adjusted or planned again;
    --publish retries the same saved content.
  • Excluded IDs stay out of new comments. The planner receives the adjusted
    findings, and the assembled preview is checked too. When a retained
    finding's summary names an excluded ID, publication is held until you
    exclude that finding as well or restore the other. References without the
    ID cannot be detected by this check.
  • Earlier PR comments keep their text. AZPR still skips comments it already
    posted and never edits them. An adjusted review's receipt names items whose
    actual text differs from the preview, including comments that appear only
    when AZPR reads the threads back. It also counts other AZPR comments on the
    PR, where an excluded finding may still be visible.
  • The README opens with a real OpenCode 2.1.4 recording of adjusting findings
    and publishing, and the README and quickstart show the adjustment workflow.
    The npm package includes the code of conduct. CI actions are pinned by commit
    and updated with Dependabot.

The options work with review, deep and quick results. Quick findings remain
not independently verified. Without adjustments, comment planning and
publication retain their existing behavior. See the
commenting guide
for the complete rules.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.0

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.0'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading

For a native installation, edit its existing entry in the OpenCode
configuration's plugins list:

  • For npm, change the package specification to
    opencode-azure-devops-pr-review@0.3.0.
  • For Git, change the tag suffix to #v0.3.0.

If the entry is an object, change only package; preserve options.settingsFile
and any other options. Keep one AZPR entry and restart the OpenCode service.
External settings, the PAT file and review records remain in place; a working
configuration needs no new /pr-setup. Exact version pins are not advanced by
opencode plugin update. This release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Automatic comments remain opt-in through afterReview or a review command
flag. Use /pr-review <PR URL> --preview when you want to inspect and adjust
findings before publication.

Compatibility and validation

The tested target remains OpenCode CLI 2.1.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The validation record
separates release checks with fake services from live runs. The earlier live
adjustment runs on 1-file and 316-file Azure DevOps test PRs preceded the final
persistence and read-back fixes; a recorded live run on the 1-file test PR used
this release's runtime. None of them establish a general review accuracy score.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.0.tar.gz, with checksums in SHA256SUMS.
The README's 15-second recording of adjusting findings and publishing comes
from that live run. The earlier walkthrough of the review, preview and
publication workflow remains attached to
v0.2.0.
The demo guide
describes both recordings.

Assets 4
Loading