Skip to content

test: trigger multi-review resume path (v4 = 4.2.3) #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Svtter wants to merge 2 commits into from
Closed

test: trigger multi-review resume path (v4 = 4.2.3) #292

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e3887e
test: trigger multi-review resume path on v4 (now = 4.2.3)
Svtter Jun 28, 2026
e7ec76d
test: second push on same PR — now resume path will fire
Svtter Jun 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/multi-review.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ jobs:
git config user.email "github-actions[bot]@users.noreply.github.com"

- name: Run multi-review
uses: sun-praise/opencode-actions/multi-review@v4.2.3
uses: sun-praise/opencode-actions/multi-review@v4
with:
model: "litellm/deepseek-v4-flash"
default-team: "quality:1,security:1,performance:1,architecture:1,regression-test:1,test-value:1"
Expand Down
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,3 +262,5 @@ The initial release-notes template lives at `docs/releases/v1.0.0.md`.
- `args` is parsed as a space-delimited string, so keep complex text in environment variables like `PROMPT`
- the installer is external, so cache invalidation uses `cache-key` instead of a guaranteed version pin
- first version is optimized for GitHub-hosted or Linux self-hosted runners

<!-- third trigger: same PR, now cache exists -> resume path -->
Loading