Repository navigation
build/bake: disable build summaries in reusable workflows - #319
Merged
Merged
Conversation
Disable per-build action summaries and remove the build-summary input. A consistent summary for the reusable workflow will be added separately. Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
vvoland
approved these changes
Oct 16, 2026
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
2 participants
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.
The build and bake workflows currently generate a separate Docker Build summary for each build job. When builds are distributed across targets and platforms, these summaries clutter the workflow run summary and make it harder to get an overall view, as reported in docker/packaging#536.
Disable these summaries for now and remove the
build-summaryinput. The intended replacement is a consistent summary for the reusable workflow as a whole, rather than exposing each underlying action's summary. That consolidated summary will be handled separately in #11.