🦅 ContentHawk - Use Pre-activation steps rather than exceptions for checking issue relevance#12782
Merged
Merged
Conversation
Calinator444
changed the title
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.
Description
This PR updates
contenthawk-snapshot-doneto use pre-activation steps to check if the closed issue was relevant rather than throwing an error. This doesn't functionally change how the workflow works, but it means when the workflow is skipped it will not show up as an error in GitHub actions.Changes based on this PR (I just used GitHub scripts instead since it's easier to read): #12767
Note
This PR was Generated by the 🦅ContentHawk installer because I wanted to roll out the fix for ContentHawk in general.
Screenshot
Figure: Workflows being skipped on test repo
Fixed
#12766