Repository navigation
complain: reopen matching issues instead of filing duplicates - #14890
Merged
Merged
Conversation
The complain action found existing issues through the search API only, filtered to open issues, with fuzzy in:title matching. A rerun that failed after its issue was labeled (gha-issue, 404) and closed filed a new issue, and two platforms failing together could both miss each other's fresh issue because the search index lags. Now it matches titles exactly, from the REST issue list (consistent immediately) plus search (for older issues). It logs to the oldest open match; otherwise it reopens the latest match closed as completed and drops its triage label so relabeling closes it again; one closed as not_planned (yanked, old-version) gets the log without reopening. After filing a new issue it re-lists, and if an older open issue with the same title exists, closes its own as a duplicate and logs there. Log comments now name the failing platform and link the run attempt. Exercised: shellcheck, actionlint, and DRY_RUN=1 against live pantry issues (open-duplicate, reopen with 404 and gha-issue labels, fuzzy near-miss title, unknown package). Not exercised: the real writes, which only run when a build fails in CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jhheider
force-pushed
the
complain-reopen
branch
from
October 25, 2026 21:01
07427c9 to
535c0fe
Compare
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
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.
The complain action found existing issues through the search API only,
filtered to open issues, with fuzzy in:title matching. A rerun that
failed after its issue was labeled (gha-issue, 404) and closed filed a
new issue, and two platforms failing together could both miss each
other's fresh issue because the search index lags.
Now it matches titles exactly, from the REST issue list (consistent
immediately) plus search (for older issues). It logs to the oldest open
match; otherwise it reopens the latest match closed as completed and
drops its triage label so relabeling closes it again; one closed as
not_planned (yanked, old-version) gets the log without reopening. After
filing a new issue it re-lists, and if an older open issue with the
same title exists, closes its own as a duplicate and logs there. Log
comments now name the failing platform and link the run attempt.
Exercised: shellcheck, actionlint, and DRY_RUN=1 against live pantry
issues (open-duplicate, reopen with 404 and gha-issue labels, fuzzy
near-miss title, unknown package). Not exercised: the real writes,
which only run when a build fails in CI.
🤖 Generated with Claude Code