PR review runs outdated WuMing and reports low-severity findings #18
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
marvin8/xique#18
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
pr-reviewCI job still pins WuMing 0.11.0, and it posts inline review comments at every severity level — including low-severity nits that drown out the findings worth acting on.Two things wanted:
Findings from exploration:
.forgejo/workflows/ci.ymlpinshttps://forge.marvin8.zone/marvin8/wuming@0.11.0in thepr-reviewjob; no other file references the wuming version.WUMING_MIN_SEVERITY(valid values:low,medium,high,critical; fail-closed on anything else) exists since 0.11.0 and is still env-only in 0.12.0 — I verified theaction.ymlat ref0.12.0via the forge API and it defines nomin_severityinput. So it must be set in a step-levelenv:block alongside thewith:inputs.Plan of attack:
pr-reviewstepuses:ref from@0.11.0to@0.12.0.env: WUMING_MIN_SEVERITY: mediumto that same step.Branch:
chore/issue-18-wuming-0.12.0-medium-floorCommits:
:construction_worker: ci: bump wuming to 0.12.0 and floor findings at medium severityPR: opened via Forgejo API (
POST /repos/marvin8/xique/pulls, headchore/issue-18-wuming-0.12.0-medium-floor, basemain,Closes #18).