You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ccfa72b
Browse filesBrowse the repository at this point in the historyBrowse files
feat(output): expose the rendered report and fix the fork-PR comment pattern
The two-workflow pattern in docs/fork-pr-comments.md and examples/ told
Workflow A to upload `result.txt`, a file the action has never written, and
did so without `if: always()`, so on the failing runs that need a comment
the upload step never ran at all. Workflow B then re-rendered a comment
under a title the action no longer recognises as its own, and read the PR
number from `workflow_run.pull_requests[0]`, which is empty for fork PRs.
Add a `report` output beside `result`: the Markdown report byte for byte,
marker to footer, written to GITHUB_OUTPUT in the same heredoc form. A
workflow_run job can post it verbatim, so the fork comment is identical to
one the action posts itself and a later `pr-comments: true` run adopts it
instead of adding a second one.
Rewrite the doc and both examples around it: Workflow A saves report.md,
result.json and pr-number under `if: always()`; Workflow B downloads by
run id and updates the comment carrying `<!-- commit-check-action -->`.
Document the output in the README and fix the diagram labels.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018xYa7m3qup5wyN5MaXFgf6
Copy file name to clipboardExpand all lines: action.yml
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,9 @@ outputs:
44
44
# mapping (and the step id it refers to) the output is always the empty
45
45
# string, and fromJSON('') fails the calling workflow.
46
46
value: ${{ steps.commit-check.outputs.result }}
47
+
report:
48
+
description: The rendered Markdown report, byte for byte what the job summary and PR comment show. Save it as an artifact from a pull_request run and post it verbatim from a workflow_run job to comment on fork pull requests (see docs/fork-pr-comments.md).
0 commit comments