Two steps in the same job both append Markdown tables to the job summary. What is the correct way to ensure both tables appear on the run summary page?
Select an answer to reveal the explanation.
Short Explanation and Infographic
GITHUB_STEP_SUMMARY is an appendable file for the job—multiple steps can add Markdown and GitHub renders the combined summary. It is not last-write-wins only, not artifact-only, and Markdown is supported.
Full explanation below image
Full Explanation
The runner exposes GITHUB_STEP_SUMMARY as a file path. Steps should append content so earlier summary sections remain. GitHub renders the aggregated Markdown on the workflow run summary for that job after the job completes. Replacing the file without care can wipe prior content; append is the usual pattern. Artifacts are optional downloads and do not replace the summary UI. The deprecated set-output command is unrelated to job summaries. Size limits apply, so keep summaries concise—link to artifacts for large reports. Combining summaries with ::notice::/::error:: annotations gives both overview and line-level detail.