ci: send the plan table to the job log as well as the summary - #29
Merged
Conversation
$GITHUB_STEP_SUMMARY renders in the run's Summary tab but never appears in the job log, and the log is what you have when reading back a finished run -- so the resolved publish/release decisions were invisible on both master runs. tee -a puts them in both. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #22.
The
planjob wrote its table only to$GITHUB_STEP_SUMMARY. That renders on the run's Summary tab, but it never reaches the job log — so on both master runs so far (30779907245,30866081633) the resolved publish/release decisions were not readable when going back over a finished run, which is exactly when you want them.tee -aputs the table in both places.Running the real step script (extracted from the workflow,
${{ }}substituted for a master push) gives identical output on stdout and in the summary file:which is also an independent check of the master row that #22 could only trace.
One line of behaviour change, in a job that does nothing but print. Note that a PR build for this is pure overhead —
paths-ignoreonly excludes**/*.md, so touching the workflow triggers the full matrix. Merging straight away (or pushing this to master directly) loses nothing.