Repository navigation
feat(workflow): close issues of recovered packages - #53
Merged
Merged
Conversation
The step runs in publish, before the step that opens issues.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Close issues of recovered packagesruns inpublishbefore the issue step and closes the open issue of a package that recovered, with a comment that names the new status and the run.❌ <package>: check failedcloses once the status is anything butcheck_failed, and❌ <package>: update failedonce it isup_to_date,updatedordowngrade. The step runs first because an open issue of a package holds back a new one, and it does not run after a failed step. With Issues turned off it does nothing. Titles are compared exactly, over up to 1000 open issues, as in the issue step.The issue body now says that a run closes it.
docs/WORKFLOW.md5.3 and 5.6 describe the step.