docs: contagem de testes e registro do review (v0.5.3) - #18
Conversation
As duas regressões adicionadas na rodada de review (continuação de cabeçalho `#` e symlink) mudaram a contagem depois que o CHANGELOG e as release notes já estavam escritos. Session-log ganha a seção do review: dois bugs reais, e a contradição entre a skill dizer "não precisa regenerar ao editar o corpo" e o CI falhar exatamente nesse caso. O defeito nasceu de eu documentar o comportamento que imaginei ter implementado. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 35 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughDocumentation updates record 19 Codemap tests, 94 total tests, symlink-boundary validation, review findings, and corrected regeneration guidance. ChangesCodemap coverage documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 281: Update the README test-count description for the node --test command
so it does not label all 94 tests as unit tests; use the neutral wording “94
tests” or provide separate unit and integration counts, accounting for the
integration test in scripts/test/codemap.test.js.
In `@session-log/2026-08-08-v0.5.3-codemap.md`:
- Around line 79-91: Atualize a seção que descreve os dois bugs corrigidos para
registrar explicitamente quando os respectivos testes de regressão foram
adicionados, deixando claro que isso ocorreu após a redação inicial desta
documentação. Preserve os detalhes existentes sobre os defeitos, a correção e a
cobertura.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 1cf36fed-6396-47f1-b6d3-1a046a2519a5
📒 Files selected for processing (4)
CHANGELOG.mdREADME.mdRELEASE-NOTES-v0.5.3.mdsession-log/2026-08-08-v0.5.3-codemap.md
… entraram O README classificava os 94 como unitários, mas o teste de symlink roda o gerador num repo temporário via execFileSync — é integração. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ajustes de acerto de contas do v0.5.3, sem mudança de comportamento.
#descartada) e a contradição entre a skill afirmar "não precisa regenerar ao editar o corpo" e o CI falhar exatamente nesse caso.O registro dessa terceira importa mais que os números: o defeito nasceu de documentar o comportamento imaginado em vez do implementado, que é uma classe de erro que nenhum teste pega.
🤖 Generated with Claude Code
Summary by CodeRabbit