Repository navigation
fix(ci): create Sound update pull requests as drafts - #643
Conversation
Dependency Review✅ No vulnerabilities or license issues found.Scanned FilesNone |
|
Reviewed exact head Examined the complete two-file diff, surrounding Sound updater workflow, App token and permissions boundary, ownership and branch lease checks, new-versus-existing pull-request paths, and the executing-shell regression. Fresh-context independent reviewer New PR creation sends JSON boolean Local validation: 81 focused workflow/Sound tests ran (78 passed; 3 unrelated CMake prerequisite skips); independent workflow validation ran 60 tests (57 passed; the same 3 environment skips). The old creation payload fails the new regression. Import-history verification (five components), Python compilation, diff whitespace, actionlint 1.7.12 and ShellCheck 0.11.0 passed. Native/hosted CI remains separately required and is not claimed by these local results. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Create new Sound update pull requests as drafts. The updater currently omits
draft: true, so a fresh dependency PR opens as ready before independent review and required delivery checks.Implementation / behavior
draft: trueonly to the new-PR POST payload.Validation
a5a2cbe5563a5917e26906d2715f5af1d68ea8ab, including Classic validation and CodeQL. The exact-head self-review receipt is posted.Limitations / follow-up
This change does not delete the stale branch, run the updater, merge a PR or deploy anything. Once the owner merges this repair, the already-approved exact branch cleanup and current-main updater run can proceed, producing a draft Sound runtime PR.