Repository navigation
feat(issues): add GitLab, Azure DevOps, and Forgejo issue trackers - #19261
juliusmarminge wants to merge 1 commit into
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosNo All 64 scenario measurements
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
771f16e to
322d00c
Compare
322d00c to
430ff17
Compare
430ff17 to
19d3c80
Compare
22b2b43 to
d927a3b
Compare
|
Taking over this one as maintainer for batch pull-request-15. I will isolate the host adapters from the stale UI base, minimize the implementation and tests, and verify Azure response decoding and comment pagination. Any host integration that cannot be verified here will remain unpublished and be reported blocked with exact follow-up steps. No merge is planned. |
|
Batch pull-request-15 outcome: blocked on live host proof. The body now records the exact verification steps and capability limits. Four full independent review rounds completed; both final reviewers found no new confirmed code defect in the local rebuild. 219 focused regression tests pass, along with scoped checks and isolated server startup. No replacement branches or PRs were published, and this draft remains open at its original head. The verified local bundle, patch, reviews, reports and restoration instructions are preserved on fs-40 at |
37f2090 to
11d6276
Compare
11d6276 to
f05d572
Compare
Each host's driver now provides its issue tracker over the CLI its pull request reads already use. Azure DevOps keeps work items per project, so its definition says where a repository's issues live and the service reads each project once. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
f05d572 to
dd13545
Compare
Extends issue tracking from #19259 to the other git hosts.
How it works
glab,az,fj/tea).issueScope), which the server and clients both read, and the service reads each project once.Not verified live: none of the three CLIs is installed on the machine this was built on. The trackers are covered by tests against recorded response shapes.
Opus 5.5 and Fable 5.2 in Claude Code, running in T3 Code.
🤖 Generated with Claude Code