Repository navigation
Conversation
Three composite actions that publish an armed pull request's built site to <site>-pr<N>.staged.apache.org, with a review overlay that turns a marked region into a screenshot and a link to its diff line. preview-annotate stamps source lines for Jekyll and Astro builds; preview-artifact packages any static site; preview-publish publishes, retires and cleans up. Extracted from apache/magpie-site, with generic names. Generated-by: Claude Opus 5
|
Extracted it from Magpie work - while working on new website, I developed this action/tooling that makes PR to the website possible to render on staging system of ASF and select areas of the website and get the comments back to the actual lines of code in PR that created it. 
How it looks like after selecting the part of the website: 
And then you get redirected to the line in the PR that produced the selected part -> and you can ctrl+v the screenshot with the area selected. |
Ports apache/magpie-site apache#208, apache#210, apache#212 and apache#214 onto the extracted actions, keeping the generic names: - Arm with the `preview` label (a /show-preview comment or a dispatch adds it); publish on workflow_run / issue_comment, not a schedule. - Project every GitHub response so the publisher never reads PR content; the build computes the diff anchors (write-meta.mjs). - Post a new comment on each publish, and lead with the preview URL. - New preview-main-overlay action: the overlay on the published site, where a comment opens an issue. Generated-by: Claude Opus 5
|
Updated screenshots from Magpie new site - also works on published site - not only on PR: 
|
The actions keep their names and tag prefixes; only the path changes, to website-comment/<action>. Generated-by: Claude Opus 5
potiuk
changed the title
Ports apache/magpie-site apache#211: ubuntu-slim cannot start a job container, so Ruby, Bundler and a C toolchain come from apt and gems go to a writable user gem home instead of the pinned ruby:3.3 image. Generated-by: Claude Opus 5
|
Gentle ping @dfoulks1 @ppkarwasz - this has been waiting for review for a while; CI is green. A quick look would be appreciated. Drafted-by: Claude Code (Opus 5.5); reviewed by @potiuk before posting |
1 participant
Composite actions that publish an armed pull request's built site to
<site>-pr<N>.staged.apache.org, with a review overlay that turns a marked region into a screenshot and a link to its diff line. Extracted from apache/magpie-site (in sync up to #219), with generic names.preview-annotatestamps source lines for Jekyll and Astro builds.preview-artifactpackages any static site, plus the diff-line anchors computed in the unprivileged build.preview-publishpublishes, retires and cleans up. A PR is armed by thepreviewlabel (added directly, by a/show-previewcomment, or by dispatch), and the publisher runs onworkflow_run/issue_comment, neverpull_request_target. Every GitHub response is projected, so it never reads PR content.preview-main-overlay(optional) puts the same overlay on the published site, where a comment opens an issue.Test plan
npm testinwebsite-comment/(163 tests, includingboundary.test.mjs: a full publisher run against baited responses and an endpoint allowlist)website-comment-test.yml: Jekyll adapter end to end (onubuntu-slim, Ruby from apt),preview-main-overlayon a small site, andpreview-publishrefusing apull_requesteventuv run pytest scripts/test_release_actions.py🤖 Generated with Claude Code