mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2273] $GITHUB_STEP_SUMMARY is unusable for any nontrivial workflow #1062
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1062
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jsoref on GitHub (Apr 4, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2273
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_SUMMARYother than the last step will be inaccessible at job completion."What GitHub does is move the contents from
$GITHUB_STEP_SUMMARYto 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_SUMMARYfile somewhere (and provide a new file for the next step -- this part is done).$GITHUB_STEP_SUMMARYfile 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
@ChristopherHX commented on GitHub (Apr 6, 2024):
My downstream act-based project explains it like
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
@jsoref commented on GitHub (Apr 7, 2024):
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
actto generate a directory using the equivalent ofmktemp -dand dump the files there (and report the directory that contains the step summaries at the end of the act run).@github-actions[bot] commented on GitHub (Mar 26, 2025):
Issue is stale and will be closed in 14 days unless there is new activity
@jsoref commented on GitHub (Mar 26, 2025):
Still relevant
@ChristopherHX commented on GitHub (May 17, 2025):
@jsoref Please test branch log-parsed-commands-and-summary
Step summary now logged, use json logger for parsing and regular logger to see the summary file content in plain text
@ChristopherHX commented on GitHub (May 17, 2025):
json