Skip to content

ci: use commit message as promotion PR title and body#36

Merged
herikwebb merged 1 commit into
mainfrom
automation/promote-body-from-commit
Jul 4, 2026
Merged

ci: use commit message as promotion PR title and body#36
herikwebb merged 1 commit into
mainfrom
automation/promote-body-from-commit

Conversation

@herikwebb

Copy link
Copy Markdown
Owner

What

promote-upstream.yml now derives the upstream PR title from the commit subject and the body from the commit message body (leading blank lines stripped), instead of a generic one-line placeholder that gave maintainers no context.

Also: when an open PR from the branch already exists, the job now refreshes it via gh pr edit rather than skipping — so re-running the workflow repairs the description of an already-open promotion PR (e.g. plmbr#386).

Why

The first promotion opened a PR whose body was just "Automated promotion … after review sign-off." — useless to upstream reviewers. The security fix commit already documents the vulnerability, attack path, and fix rationale; that content should be the PR body.

Effect

Re-dispatching Promote to upstream for security/fix-search-files-symlink-20260704031032-3406 will update the open upstream PR's body to the full commit message.


Generated by Claude Code

The promote workflow wrote a generic one-line body that gave upstream
maintainers no context. Derive the PR title from the commit subject and the
body from the commit message body (leading blank lines stripped), and refresh
an already-open PR via gh pr edit instead of skipping, so a re-run repairs an
existing promotion PR's description.
@herikwebb herikwebb added the enhancement New feature or request label Jul 4, 2026 — with Claude
@herikwebb herikwebb merged commit c172ec3 into main Jul 4, 2026
5 checks passed
@github-actions

github-actions Bot commented Jul 4, 2026

Copy link
Copy Markdown

Automated PR Review

Model: gpt-5.5
Verdict: APPROVE

Changed files:

.github/workflows/promote-upstream.yml

Review result:

No automated findings were found. The workflow changes appear to safely quote user/commit-derived values and preserve the existing idempotent behavior while updating PR metadata. Residual risks include operational edge cases around manual branch input validity and the PAT/environment protection configuration, which are outside the diff’s direct correctness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant