In $GITHUB_STEP_SUMMARY
, enclosing content in a multi-step <details>
tag will place the content outside of that tag.
#44185
Unanswered
korosuke613
asked this question in
Actions
Replies: 1 comment
-
I'm in the same boat, hoping I could use disclosure elements to encapsulate any trailing step summaries. The latest release of the docker build/bake actions can now generate its own build summaries:
However, these new docker build summaries can be a bit verbose, so rather than disabling them, I'd simply like to hide them via a disclosure element whose visibility can be toggled on or off. However, the enforced isolation between steps prevents this:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Body
Summary
In
$GITHUB_STEP_SUMMARY
, enclosing content in a multi-step<details>
tag will place the content outside of that tag. The raw markdown had content inside<details>
.There is a workaround, but it is a bit inconvenient 🥲
Background
I want to be able to dynamically enclose $GITHUB_STEP_SUMMARY in a
<details>
tag so that the display is not too large. So I separate the steps.Actual
https://github.com/korosuke613/playground/actions/runs/3908450732#summary-10622165892
workflow
For simplicity, we use
env
to set the variables in theDETAILS
.created summary
2023-01-13.13.27.13.mov
raw markdown
Click
View raw markdown
.https://github.com/korosuke613/playground/actions/runs/3908450732/jobs/6678608781/summary_raw
Expected
https://github.com/korosuke613/playground/actions/runs/3908450732#summary-10622165968
created summary
2023-01-13.13.27.31.mov
Note
I was able to work around this problem by compiling the output to a separate file and then appending it to
$GITHUB_STEP_SUMMARY
.workflow
Beta Was this translation helpful? Give feedback.
All reactions