Skip to content

Teach the Copilot Reader the Unresolved Findings Label - #3514

Merged
ptr727 merged 1 commit into
developfrom
feature/copilot-unresolved-findings-label
Oct 27, 2026
Merged

ptr727 merged 1 commit into
developfrom
feature/copilot-unresolved-findings-label

Conversation

@ptr727

@ptr727 ptr727 commented Oct 27, 2026

Copy link
Copy Markdown
Owner

Summary

Copilot's review overview now introduces its remaining findings under an Unresolved findings: label. The Copilot reader in scripts/reviewers/copilot.json listed that spelling in neither labels nor finding_lists. As a result, pr_review.py status reported the part as unplaced, and a finding that appeared only in the body was not counted as unthreaded.

Changes

  • Add unresolved findings: to both labels and finding_lists, the same way open findings remain: is listed. Adding it to labels alone, which is what Teach the Copilot Reader the Unresolved Findings Label #3513 proposed, would only silence the notice. The body-only finding would still be missed, because finding_lists is what counts listed items against linked threads.
  • Add one test that runs each top-level finding-list spelling through a constructed body. Each case asserts one unthreaded finding, no notes, and nothing unplaced. Before the fix, the test failed only on the new spelling, with unthreaded at 0 where 1 was expected.

Verification

  • The full suite passes under uv run --no-project --with-requirements tests/requirements.txt python -m unittest discover -s tests: 3037 tests OK, 7 skipped.
  • The hub's .husky/pre-commit gates pass: ruff format and lint, mypy, the prose gate, and eol.
  • A local strict review ran at the frontier tier over this diff with zero findings. It is recorded as agent-skill against develop.

Refs #3513, which the promotion pull request closes.

🤖 Generated with Claude Code

Copilot's overview now introduces its remaining findings under an
"Unresolved findings:" label, which the reader listed in neither its
labels nor its finding lists, so the part read as unplaced and a
finding present only in the body went uncounted as unthreaded. Add the
spelling to both lists, as "open findings remain:" is, with a case per
top-level finding-list spelling built from a constructed body.

Closes #3513

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings October 27, 2026 01:13
@ptr727

ptr727 commented Oct 27, 2026

Copy link
Copy Markdown
Owner Author

A recorded local strict-review pass covers head 313eead2290767d6c5fa59c6a6c73349d7b7c1cc, the content this pull request carries at that commit against develop, and it recorded 0 findings.

@coderabbitai

coderabbitai Bot commented Oct 27, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

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

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes are focused, regression-tested, and no unresolved review issues remain.

No open issues 🎉

What changed in this PR

Updates the Copilot review-body reader to recognize and count findings under the Unresolved findings: heading.

Changes:

  • Adds unresolved findings: to the recognized labels and finding-list patterns.
  • Adds regression coverage for all supported finding-list spellings.
File Description
tests/​test_pr_review_copilot.py Verifies supported finding-list labels produce the expected unthreaded count without notes or unplaced content.
scripts/​reviewers/​copilot.json Registers the new Copilot findings label and list spelling.

Review effort: Lite

@codecov

codecov Bot commented Oct 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.54%. Comparing base (1ab4c89) to head (313eead).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #3514   +/-   ##
========================================
  Coverage    81.54%   81.54%           
========================================
  Files           26       26           
  Lines         8918     8918           
========================================
  Hits          7272     7272           
  Misses        1646     1646           
Flag Coverage Δ
python-3.13 81.54% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ptr727
ptr727 merged commit 3dbbe67 into develop Oct 27, 2026
14 checks passed
@ptr727
ptr727 deleted the feature/copilot-unresolved-findings-label branch October 27, 2026 01:24
ptr727 added a commit that referenced this pull request Oct 27, 2026
## Summary

This promotes
[#3514](#3514) to `main`.
That change teaches the Copilot reader the `Unresolved findings:` label
in both its `labels` and `finding_lists`, so a finding listed there is
placed and counted against the linked threads.

Closes #3513

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants