You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a boolean output to indicate if the image was pushed #446
Please add an output that indicates whether or not the image was successfully pushed.
This can be useful in cases where the push may be filtered out, and rather than repeating the same filter on a subsequent step it would be simpler to condition it based on the output from this action. For example:
I checked the current action: registry pushes happen in the job’s post step, so a wasPushed output there would arrive too late for the attestation step in the example.
Would you consider an opt-in mode that publishes before the build step returns, while leaving the default job-end push unchanged? In that mode, wasPushed would be true only after all requested pushes succeed and false if the filters skip publishing. Push failures would still fail the step. The attestation example should use the published manifest digest rather than docker inspect .Id.
Is that direction worth a PR? Should the first version cover both GitHub Actions and Azure DevOps, or start with GitHub Actions?
Would you consider an opt-in mode that publishes before the build step returns
This is how I thought it worked for a long while, actually, so I got really confused when tried to extract the digest (for attestation reasons) and it kept coming up empty.
Frankly, doing it as a post step makes it impossible to do anything with the pushed image in the same job, because post doesn't happen until the job ends (not the action).
Activity
sinbumu commentedon Nov 19, 2026
I checked the current action: registry pushes happen in the job’s
poststep, so awasPushedoutput there would arrive too late for the attestation step in the example.Would you consider an opt-in mode that publishes before the build step returns, while leaving the default job-end push unchanged? In that mode,
wasPushedwould be true only after all requested pushes succeed and false if the filters skip publishing. Push failures would still fail the step. The attestation example should use the published manifest digest rather thandocker inspect .Id.Is that direction worth a PR? Should the first version cover both GitHub Actions and Azure DevOps, or start with GitHub Actions?
Clockwork-Muse commentedon Nov 19, 2026
This is how I thought it worked for a long while, actually, so I got really confused when tried to extract the digest (for attestation reasons) and it kept coming up empty.
Frankly, doing it as a post step makes it impossible to do anything with the pushed image in the same job, because post doesn't happen until the job ends (not the action).