Skip to content

mi355x dsv4 retry #1160

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

Merged
Oseltamivir merged 1 commit into from
Apr 25, 2026
+8 −0

mi355x dsv4 retry

2e1ce99
Select commit
Loading
Failed to load commit list.
Merged

mi355x dsv4 retry #1160

mi355x dsv4 retry
2e1ce99
Select commit
Loading
Failed to load commit list.
Claude / Claude Code Review completed Apr 25, 2026 in 6m 25s

Code review found 1 potential issue

Found 5 candidates, confirmed 1. See review comments for details.

Details

Severity Count
🔴 Important 0
🟡 Nit 1
🟣 Pre-existing 0
Severity File:Line Issue
🟡 Nit perf-changelog.yaml:1830-1836 pr-link should reference this PR (#1160), not #1159

Annotations

Check warning on line 1836 in perf-changelog.yaml

See this annotation in the file changed.

@claude claude / Claude Code Review

pr-link should reference this PR (#1160), not #1159 

The newly added perf-changelog entry sets `pr-link: .../pull/1159`, but this is PR #1160 ("mi355x dsv4 retry"); #1159 is the prior already-merged retrigger PR (commit d578b7e). The entry was copy-pasted from the unlinked block above without bumping the number — following the convention used for the analogous retrigger pattern at lines 1799-1805 (where #1148 self-references), this should point to `pull/1160`.
View more details on Claude