Cursor Agent f876173b78 feat(triage): 1-day grace period before close + SwiftWinds immediate-close bypass ... - Add a 24-hour grace window between the first low-quality detection and the actual auto-close. The first detection posts a warning comment that explicitly says "You have 1 day to address this before this PR is auto-closed" and points the contributor at: * `@agent-shin reconsider` to request another look (and re-open) * `@greptileai` to request a fresh Greptile review — works even after the PR is closed - Both `triage_with_llm.py` (LLM judge) and `close_low_quality_prs.py` (Greptile-score closer) share the same `<!-- agent-shin:grace-warning -->` HTML marker so a warning posted by either path is recognized by both. - Add IMMEDIATE_CLOSE_LOGINS = {swiftwinds} to bypass BOTH the grace period AND the dry-run / AGENT_SHIN_ENABLED gating. SwiftWinds is the user's personal account (no push permissions to litellm) used to dogfood the bot; user explicitly asked: "For SwiftWinds, just close immediately. Faster iteration that way." - Update the standard close comments to mention that `@greptileai` works even after the PR is closed. - Add 23 new tests covering: warn-grace on first detection, skip during grace window, close after grace expires, SwiftWinds bypass (case insensitive, with close=False, no random-login false positives), the grace-warning text invariants, and the SwiftWinds entry in the IMMEDIATE_CLOSE_LOGINS constant. Co-authored-by: Mateo Wang <mateo-berri@users.noreply.github.com>		2026-05-19 07:35:24 +00:00
..
close_duplicate_issues.py	style: run black formatter on files from main merge	2026-04-17 13:02:59 -07:00
close_low_quality_prs.py	feat(triage): 1-day grace period before close + SwiftWinds immediate-close bypass	2026-05-19 07:35:24 +00:00
scan_keywords.py	style: run black formatter on files from main merge	2026-04-17 13:02:59 -07:00
triage_with_llm.py	feat(triage): 1-day grace period before close + SwiftWinds immediate-close bypass	2026-05-19 07:35:24 +00:00