Skip to content

fix(ci): silence English translation noise and harden related-issue matches - #458

Merged
Wibias merged 13 commits into
lidge-jun:devfrom
Wibias:fix/issue-bot-noise
Jul 25, 2026
Merged

fix(ci): silence English translation noise and harden related-issue matches#458
Wibias merged 13 commits into
lidge-jun:devfrom
Wibias:fix/issue-bot-noise

Conversation

@Wibias

@Wibias Wibias commented Jul 25, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Collaborator

Summary

  • Reduce issue-bot noise for English/no-translation paths by storing cooldown and rate-limit state in a bot-owned marker-only control comment (no visible English bookkeeping text).
  • Keep non-English translations on the existing visible bookkeeping comment path.
  • Preserve author whitespace when stripping orphan body control markers; require concrete shared failure signatures before keeping related-issue matches that use weak “same client/app” wording; unify the no-translation model prompt so detected_language stays the source language (normally English) with empty translation fields.

English-state contract

  • No visible English bookkeeping text for English/no-translation results (marker-only github-actions[bot] control comment).
  • Authoritative cooldown/rate-limit state is the verified bot-owned control comment only.
  • Issue title/body are never used as authoritative control state; forged body markers are ignored and stripped as non-authoritative orphans.
  • Author-created comments that contain the control marker are never trusted.
  • Canonical comment create/update completes first; redundant older bot control comments are deleted only after that succeeds.
  • Create/update failures preserve the previous durable comment; cleanup failures leave redundant comments as fallback.
  • No Actions cache / .ocx-translation-state file path (issue-triggered workflows cannot durably save cache entries).

Test plan

  • node --test .github/scripts/issue-translation.test.cjs
  • node --test .github/scripts/issue-triage.test.cjs
  • node --test .github/scripts/parse-issue-translation-response.test.cjs
  • node --test .github/scripts/issue-quality.test.cjs
  • bun test tests/ci-workflows.test.ts
  • Issue quality tests workflow
  • React Doctor
  • Cross-platform CI
  • Explicit maintainer security approval for .github/** changes before merge

Summary by CodeRabbit

  • New Features
    • Improved issue triage: stricter, JSON-only match extraction with stronger “related” reasoning.
  • Bug Fixes
    • Hardened translation control-state recovery from outdated/orphan markers and time-skew issues.
    • English/no-translation attempts no longer show unnecessary visible bookkeeping.
    • Prevented issue-authored markers from overriding trusted translation state; improved canonical control-comment upsert/cleanup.
  • Tests
    • Expanded coverage for translation control-state healing and triage parsing/sanitization behavior.

@Wibias
fix(ci): silence English translation bookkeeping and harden related-i…
9cba975 
…ssue matches

Stop posting visible English translation control comments (keep rate-limit state invisible on the issue body), and drop weak "somewhat related" triage links like lidge-jun#452->lidge-jun#420.
@github-actions github-actions Bot added the bug Something isn't working label Jul 25, 2026
@coderabbitai

This comment was marked as outdated.

Sign in to view
chatgpt-codex-connector[bot]

This comment was marked as resolved.

Sign in to view

coderabbitai[bot]

This comment was marked as resolved.

Sign in to view

Wibias added 3 commits July 25, 2026 19:34
@Wibias
fix(ci): keep English translation state in bot-owned comments
4deed7f 
Address Codex/CodeRabbit review: stop trusting author-editable issue-body markers for rate limits, keep markers-only bot comments (no visible English bookkeeping), and stop rejecting concrete 'both involve' related reasons.
@Wibias
Merge remote-tracking branch 'upstream/dev' into fix/issue-bot-noise
2626650
@Wibias
fix(ci): store English translation cooldown off the issue timeline.
ebdf864 
Persist English/no-translation rate-limit state in a bot-owned Actions cache file instead of marker-only issue comments, preserve orphan-marker whitespace, require concrete related-issue signatures, and unify the no-translation prompt contract.
coderabbitai[bot]

This comment was marked as resolved.

Sign in to view

Wibias added 5 commits July 25, 2026 20:48
@Wibias
fix(ci): delete English control comments only after cache save
27f5e8c 
Keep silent file state local until Actions cache upload succeeds, then remove verified bot control comments so cancelled or failed cache saves cannot erase cooldown history.
@Wibias
fix(ci): restore marker-only bot comments for English cooldown state
b3ce397 
Issue-triggered workflows cannot durably save Actions cache entries, so keep cooldown history in a github-actions control comment without visible English bookkeeping and drop the non-durable file/cache path.
@Wibias
fix(ci): harden triage related matching and translation state safety
c48d45a 
Require per-related shared-failure reasons, strip orphan body markers only at EOF, and reject far-future cooldown timestamps so poisoned bot comments cannot lock rate limits.
@Wibias
fix(ci): reject related matches with distinct failure signatures
5de9a1c 
Require shared-failure wording (not use/call/involve overlap) and drop reasons that carry multiple HTTP statuses or contrast attributions.
@Wibias
fix(ci): require shared quantifiers to bind to concrete failure tokens
0f645e4 
Reject related reasons where generic both-fail wording borrows a one-issue errno/status/Field required token, while keeping clause-bound shared signatures.
coderabbitai[bot]

This comment was marked as resolved.

Sign in to view

coderabbitai[bot]

This comment was marked as resolved.

Sign in to view

Wibias added 4 commits July 25, 2026 22:03
@Wibias
fix(ci): address CodeRabbit findings on triage and translation durabi…
2085017 
…lity

Tighten errno/HTTP signature matching, pass injected now into control-comment
selection, improve persist-failure observability, and cover the paginate cleanup path.
@Wibias
test(ci): lock related matcher against issue-number signature collision
6515086 
Cover phrasing where a shared verb binds both issues to another ticket number
rather than a real failure or HTTP status code.
@Wibias
fix(ci): reject mixed HTTP/errno related failure signatures
a6b0b67 
Treat HTTP status plus errno as distinct failures, and stop generic both-fail
wording from binding later issue-specific tokens as shared evidence.
@Wibias
fix(ci): treat this/current/present issue as one-sided related attrib…
af8711d 
…utions

Extend ISSUE_SPECIFIC_ATTR_RE so generic both-fail wording cannot bind tokens
attributed to this, current, or present issue.
@Wibias
Wibias merged commit 233f3f8 into lidge-jun:dev Jul 25, 2026
10 checks passed
This was referenced Jul 25, 2026
Closed
Closed
Closed
Closed
Merged
Merged
Merged
@lidge-jun lidge-jun mentioned this pull request Jul 25, 2026
Merged
7 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Jul 26, 2026
Merged
4 tasks
@Wibias
Wibias deleted the fix/issue-bot-noise branch July 27, 2026 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments
@chatgpt-codex-connector chatgpt-codex-connector[bot] chatgpt-codex-connector[bot] left review comments
@lidge-jun lidge-jun Awaiting requested review from lidge-jun lidge-jun is a code owner
@Ingwannu Ingwannu Awaiting requested review from Ingwannu Ingwannu is a code owner

Assignees

No one assigned

Labels

bug Something isn't working

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Wibias