Auto-close linkback-only bot issue shells in triage workflow

[Copilot]

Canonical issue

Linked by automation.

Outcome

Bot-created “Addressing Issues” shells that contain only the Linear linkback block are now treated as empty shells and auto-closed before triage labels are applied, eliminating recurrent triage noise.

Scope

• Included:
  • Workflow logic: /\.github/workflows/issue-triage.yml now normalizes and strips the Linear linkback marker+anchor block before emptiness checks.
  • Regression test: added tests/unit/test_issue_triage_workflow.py to execute the embedded actions/github-script and assert close-vs-label behavior for a linkback-only bot issue body.
  • Behavioral invariant: auto-close path comments + closes; triage-label path is skipped.
  • Snippet:

    const bodyWithoutLinearLinkback = body
      .replace(/<!--\s*linear-linkback\s*-->/gi, '')
      .replace(/<p>\s*<a\s+href="https:\/\/linear\.app\/[^"]+">[^<]*<\/a>\s*<\/p>/gi, '')
      .trim();
    const linearLinkbackOnly = body !== '' && bodyWithoutLinearLinkback === '';

• Explicitly excluded:
  • Label taxonomy/rules changes
  • Non-bot issue triage behavior
  • Any workflow outside issue-triage.yml

Risk

• Risk level: low
• Failure mode: overly broad body stripping could close unintended bot issues if future formatting differs but matches current regex.
• Rollback: revert issue-triage.yml logic and remove the new regression test.

Verification

List exact automated and manual checks, tied to the current head SHA.

Head: e98a723

• Focused tests
  • python -m pytest tests/unit/test_issue_triage_workflow.py -q -o addopts=''
• Required CI
  • parallel_validation (Code Review + CodeQL Security Scan) completed with no actionable findings
• Review threads resolved

Production evidence

Not applicable: this change updates GitHub issue triage automation and unit coverage only; no runtime app deployment surface is affected.

Agent handoff

• One canonical issue is linked
• No competing PR implements the same issue
• Acceptance criteria are satisfied
• Required checks pass on the current head
• Human decision is requested only for product, security, irreversible infrastructure, or production approval

• Fixes Addressing Issues #1553

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
v0-uvai	Ready	Preview, v0	Sep 8, 2026 11:45pm UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 250dea9d-7098-49c3-bb66-42de2ae192f3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Backlog triage: leaving open. Bot-shell auto-close is useful (#1553/#1523) but CONFLICTING. Rebase, or Hayden can close the empty issue shells directly (this agent has no issue-write).

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA e98a723.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

[github-actions]

🔍 PR Validation

⚠️ PR title should follow conventional commits format

[github-actions]

⚠️ Repository reconciliation: this PR does not reference exactly one canonical issue.

Please add a Closes #<issue> reference in the PR description so it can be tracked against the delivery plan.

See governance: #898