octoguard: move zizmor job within octoguard one #5
Conversation
This file contains 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
crazy-max
force-pushed
the
octoguard-repo-uses
branch
2 times, most recently
from
7ad772a to
98b661e
Compare
crazy-max
changed the title
Signed-off-by: CrazyMax <[email protected]>
crazy-max
force-pushed
the
octoguard-repo-uses
branch
from
98b661e to
4a968aa
Compare
temenuzhka-thede
approved these changes
Apr 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We can't use reusable workflows when use as org-wide workflow call: https://github.com/docker/buildx/actions/runs/14265780624
But we also can't use a git ref within the same repo on pull request event: https://github.com/docker/octoguard/actions/runs/14265913719
This relates to https://github.com/orgs/community/discussions/10679#discussioncomment-2146119
So let's just move the zizmor job within the octoguard one.