docs(issues): update templates issues - #473
Conversation
|
Warning Review limit reached
Next review available in: 37 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: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded Portuguese GitHub issue templates for bug reports, feature requests, and domain-module PRDs. The templates define metadata and structured prompts for descriptions, requirements, acceptance criteria, testing, scope, subtasks, and references. Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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 @.github/ISSUE_TEMPLATE/bug_report.md:
- Line 3: Corrija o texto de ajuda do template de reporte para usar “Descreva”
em vez de “Descreve”, preservando o restante do conteúdo.
- Line 42: Normalize the Markdown heading spacing at all listed sites: in
.github/ISSUE_TEMPLATE/bug_report.md lines 42-42 and 47-47, and
.github/ISSUE_TEMPLATE/feature_request.md lines 11-11, 16-16, 24-24, 31-31, and
52-52, reduce the two spaces after ## to one while preserving each heading’s
text.
In @.github/ISSUE_TEMPLATE/feature_request.md:
- Line 3: Corrija o texto de ajuda do template, alterando “Descreve” para
“Descreva” na propriedade about e mantendo o restante da descrição inalterado.
- Around line 35-49: Adicione `# language: pt` como a primeira linha do bloco
Gherkin no template de solicitação de funcionalidade, antes de `Funcionalidade`,
para que as palavras-chave em português sejam reconhecidas.
🪄 Autofix (Beta)
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: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Pro Plus
Run ID: 7d6acc8d-5826-4767-a649-f780a9a1cd70
📒 Files selected for processing (3)
.github/ISSUE_TEMPLATE/bug_report.md.github/ISSUE_TEMPLATE/feature_request.md.github/ISSUE_TEMPLATE/prd---módulo-de-domínio.md
fernanduandrade
left a comment
fernanduandrade
left a comment
There was a problem hiding this comment.
Ficou muito bom Sther 👏🥹
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
danielhe4rt
left a comment
danielhe4rt
left a comment
There was a problem hiding this comment.
LGTM!
(LOOKS GOOD TO ME!!!)
|
LGTM |
|
abaixo a ditadura |
|
LGTM! |
|
LGTM |
|
LGTM |
|
LGTM! |
|
LGTM! |
|
Lgtm |
|
LGTM! |
|
|
||
| ## Subtarefas | ||
| <!-- Quebra em tracer bullets, em ordem de dependência. Vincule as tasks criadas no git aqui. --> | ||
|
|
There was a problem hiding this comment.
| ## Dúvidas/Incertezas | |
| <!-- Liste aqui todas as dúvidas que ainda ficaram em aberto ou ainda precisam de maiores esclarecimentos --> | |
|
|
||
|
|
||
| ## O que construir | ||
| <!-- O que precisa ser implementado, de forma objetiva. Cite Actions, papéis, transações |
There was a problem hiding this comment.
seria interessante adicionar uma sessão de assumptions - premissas que a equipe assume como verdadeiras ao estimar e desenvolver a story, mas que ainda não foram confirmadas ou validadas.
Elas servem para deixar explícito o que está sendo considerado como certo, evitando retrabalho se alguma dessas premissas se mostrar errada depois. Exemplos:
"Assumimos que o usuário já está autenticado antes de acessar essa tela"
"Assumimos que a API de terceiros retorna os dados em JSON"
"Assumimos que não há necessidade de suporte a múltiplos idiomas nesta fase"
20 participants
Closes #467
Neste PR estou adicionando templates para as principais frentes que hoje abordados, que são features, bug's e PRD.