feat: detects well-known publisher actions in cache-audit #338
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
woodruffw
reviewed
Dec 20, 2024
woodruffw
reviewed
Dec 20, 2024
woodruffw
reviewed
Dec 20, 2024
3 tasks
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.
A first follow-up from #294. also contributing to #334
We now have a list of well-know publisher Actions (2 of them so far 😄) and the audit inspects all the steps at once alongside with the previous trigger evaluation to determine whether the Workflow/Job actually builds artifacts for publishing.
I also introduced an
PublishingArtifactsScenarioenum to easilty match the situation we are dealing with and signal properly the non-primary locations inFindingBuilders.