The publish.yml pre-release flow publishes packages but gives no visibility into what was published on the PR. In ts-npm-packages (issue couimet/ts-npm-packages#33), we landed on using marocchino/sticky-pull-request-comment@v3.0.4 to post a sticky comment listing the published package specs. The action is battle-tested, sticky (re-runs update the same comment), and has number_force for workflow_dispatch triggers where there is no PR context.
This would be the same pattern: a bash preamble step finds the PR from the branch name and builds a comment body from the publish output, then the action posts it.
The
publish.ymlpre-release flow publishes packages but gives no visibility into what was published on the PR. Ints-npm-packages(issue couimet/ts-npm-packages#33), we landed on usingmarocchino/sticky-pull-request-comment@v3.0.4to post a sticky comment listing the published package specs. The action is battle-tested, sticky (re-runs update the same comment), and hasnumber_forceforworkflow_dispatchtriggers where there is no PR context.This would be the same pattern: a bash preamble step finds the PR from the branch name and builds a comment body from the publish output, then the action posts it.