Repository navigation
docs(pro): redigir credencial e e-mail de cliente dos guias de operação Pro - #864
Pedrovaleriolopez wants to merge 1 commit into
Conversation
…ão Pro Os guias de operação de acesso Pro traziam, em texto claro, a senha e o e-mail reais de um cliente usados numa validação (desde 490ff12, PR #637), mais exemplos de comando com os mesmos valores. Troca tudo por placeholders (<validated-customer-email>, <redacted-password>, <new-strong-password>). A troca da senha da conta é feita à parte pelo founder; o histórico do git não é reescrito. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. WalkthroughOperational examples and access-operation documentation replace customer email addresses and passwords with placeholders. The documents also state that customer data and credentials must not be recorded in documentation. ChangesCredential Redaction
Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other Suggested labels: Merge Risk:
|
📊 Coverage ReportCoverage report not available
Generated by PR Automation (Story 6.1) |
Remove dos guias de operação do Pro uma credencial e um e-mail reais de cliente que estavam em texto claro desde o PR #637. No lugar entram placeholders (
<validated-customer-email>,<redacted-password>,<new-strong-password>).docs/guides/pro/access-grant-ops-playbook.md,docs/guides/pro/squad-creator-handoff-pro-access-ops.md,docs/aiox-agent-flows/devops-system.md.🤖 Generated with Claude Code
Summary by CodeRabbit