Skip to content

fix(release-management): pass PR and comment bodies through a file #1502

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
potiuk merged 1 commit into from
Oct 4, 2026
+12 −10
Merged

fix(release-management): pass PR and comment bodies through a file #1502

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions plugins/magpie-release-management/skills/announce-draft/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ argument-hint: "<version> [--planning-issue <url>]"
capability: capability:resolve
surface_hash: sha256:edffafcd9d9948ab
license: Apache-2.0
measured_tokens: 6907
measured_tokens: 6928
---

<!-- SPDX-License-Identifier: Apache-2.0
Expand Down Expand Up @@ -497,9 +497,9 @@ reviewers reported each, and every entry in `warnings` verbatim.
<!-- END MAGPIE BLOCK: pre-pr-adversarial-review -->

Present the PR title, body, and file scope to the RM. Ask for
confirmation before opening the PR. If the RM confirms, open the PR
via `gh pr create --repo <site_repo> --title "<title>" --body "<body>"
--base main`.
confirmation before opening the PR. If the RM confirms, write the
approved body to a file in the session scratch directory and open the PR via
`gh pr create --web --repo <site_repo> --title "<title>" --body-file <scratch>/announce-pr-body.md --base main`.

Return ONLY valid JSON with this structure:

Expand Down
7 changes: 4 additions & 3 deletions plugins/magpie-release-management/skills/audit-report/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ argument-hint: "<version> [--planning-issue <url>]"
capability: capability:stats
surface_hash: sha256:576d71b04f203cd8
license: Apache-2.0
measured_tokens: 6629
measured_tokens: 6651
---

<!-- SPDX-License-Identifier: Apache-2.0
Expand Down Expand Up @@ -496,8 +496,9 @@ reviewers reported each, and every entry in `warnings` verbatim.
<!-- END MAGPIE BLOCK: pre-pr-adversarial-review -->

Present the PR title, body, and target file path to the RM. Ask for
confirmation before opening the PR. If the RM confirms, open the PR via
`gh pr create --repo <upstream> --title "<title>" --body "<body>" --base main`.
confirmation before opening the PR. If the RM confirms, write the
approved body to a file in the session scratch directory and open the PR via
`gh pr create --web --repo <upstream> --title "<title>" --body-file <scratch>/audit-report-pr-body.md --base main`.

Return ONLY valid JSON with this structure:

Expand Down
7 changes: 4 additions & 3 deletions plugins/magpie-release-management/skills/rc-cut/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ argument-hint: "<version> rc<N>"
capability: capability:resolve
surface_hash: sha256:60623e456e72bbf6
license: Apache-2.0
measured_tokens: 11783
measured_tokens: 11801
---

<!-- SPDX-License-Identifier: Apache-2.0
Expand Down Expand Up @@ -786,8 +786,9 @@ The comment must include:
- The proposed next label: `rc-staging`.

Present the proposed comment to the RM. Ask for confirmation before
posting. If the RM confirms, post the comment via
`gh issue comment <planning-issue-number> --repo <upstream> --body "<body>"`.
posting. If the RM confirms, write the approved comment to a file in the
session scratch directory and post it via
`gh issue comment <planning-issue-number> --repo <upstream> --body-file <scratch>/rc-cut-comment.md`.

Return ONLY valid JSON with this structure:

Expand Down