HDDS-15725. zizmor check should reflect failure in fork#10649
Merged
Conversation
Contributor
Author
|
Thanks @peterxcli for the review. |
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.
What changes were proposed in this pull request?
zizmor workflow added in HDDS-14920 provides feedback via "Code scanning results". The workflow itself passes even if it finds issues to be fixed. This does not work well in forks where code scanning is disabled.
Example (with intentional violation):
https://github.com/adoroszlai/ozone/actions/runs/28570405264/job/84706670204#step:3:1058
To provide better feedback, the workflow should reflect scan results in forks.
Two additional minor tweaks:
https://issues.apache.org/jira/browse/HDDS-15725
How was this patch tested?
Same violation with the patch fails:
https://github.com/adoroszlai/ozone/actions/runs/28570585965/job/84707233189#step:3:208
The patch without intentional violation passes:
https://github.com/adoroszlai/ozone/actions/runs/28570809169/job/84707932173#step:3:107