-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check failed actions #62
Closed
Closed
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
Coverage after merging check-failed-actions into main will be
Coverage Report
|
@adcreare I'm thinking we keep the issue open but don't do this PR since it requires a change to existing actions. once/when/if Github provides a better hook for this then we can do a PR at that time. |
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.
Closes #61
An example of how this would work with publish is shown in https://github.com/checkdigit/hash/pull/21/files
This chains onto the publish action and evaluates the result of the previous job. Unfortunately triggering a top level job from a failure doesn't seem doable.
An alternative would be to have a scheduled action that checks every few hours. The bonus about this is it gives quick feedback for any failures on an action, this can apply to any action although it probably only makes sense to include on actions running in main and scheduled actions