The outage issue says when the site came back (#167) - #189
Merged
Conversation
The first drill of the outside check (#188) opened its issue, locked it, and closed it again when the address answered — without the comment saying when. A locked issue refuses comments from the workflow's own token too ("Unable to create comment because issue is locked"), and the `|| true` from the review round hid it. The recovery now unlocks for the one comment and locks again after; a comment that still fails warns in the run, and the issue closes regardless, because its open-or-closed state is the answer people read. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 tasks
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.
Refs #167.
The first drill of the outside check (#188) opened its issue, locked it, and closed it when the address answered — without the comment saying when. A locked issue refuses comments from the workflow's own token too (
GraphQL: Unable to create comment because issue is locked), and the|| trueadded in the review round of #184 hid it.Now the recovery unlocks for the one comment and locks again after. A comment that still fails warns in the run, and the issue closes regardless: its open-or-closed state is the answer.
Verification: after merge, the drill again —
Watchby hand withhttps://down.invalid/, then withhttps://dev.architektow3d.pl/— and the drill issue must end closed with a comment.🤖 Generated with Claude Code