Open jsoref opened 6 months ago
My downstream act-based project explains it like
Step Summaries are not implemented (only file command is provided)
I believe to have asked a while ago in another issue how act should provide the step summary...
My downstream act-based project could sent them to GitHub Actions
Introduce Cli --step-summary-output
?
-
stdout<file>
all summaries concatinated, but what about multiple jobs...Not an active developer for stuff only usefull for act cli
act has no webui like my slower alternative to it, so no fancy way to render them
Writing them somewhere into the act container that is destroyed on success by default doesn't make sense to me
I'd prefer to be able to specify a directory for step summaries.
--step-summary-directory <...>
Each file being named for a job.
If it isn't specified, I'd prefer for act
to generate a directory using the equivalent of mktemp -d
and dump the files there (and report the directory that contains the step summaries at the end of the act run).
Bug report info
Command used with act
Describe issue
While it's true that https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary says:
It doesn't mean "any content dumped into
$GITHUB_STEP_SUMMARY
other than the last step will be inaccessible at job completion."What GitHub does is move the contents from
$GITHUB_STEP_SUMMARY
to a new location which it then collates (each step's output is appended to the end of the collected output) at the end of each step.I expect act to do something similar:
$GITHUB_STEP_SUMMARY
file somewhere (and provide a new file for the next step -- this part is done).$GITHUB_STEP_SUMMARY
file and make that availableJob Summary written to: <path to local file.md>
Link to GitHub repository
https://github.com/check-spelling-sandbox/nektos-issue-step-summary-outputs-1/
Workflow content
Relevant log output
Additional information
No response