Debug with metadata, not secrets.
ReviewRouter support should be able to diagnose installation, workflow, provider, and health problems without seeing customer code, diffs, or provider credentials. Contact: quantjumppro@gmail.com
Send links and categories first.
Use the GitHub issue templates for normal setup and bug reports. If a report may include credentials, private code, tenant isolation, or security-sensitive data, email quantjumppro@gmail.com first instead of opening a public issue. Start with this shape:
To: quantjumppro@gmail.com
Repository: owner/repo
Pull request: https://github.com/owner/repo/pull/123
Workflow run: https://github.com/owner/repo/actions/runs/123456
ReviewRouter action ref: 777genius/review-router@v1
Safe error category: provider_auth_missing | codex_failed | no_inline_comments
What changed recently: setup PR merged, secret reseeded, config changedStart with the workflow run URL
The run URL gives enough metadata to identify action version, event type, and failure stage without copying secrets or source code.
Use safe error categories
Prefer categories like provider_auth_missing, codex_failed, workflow_missing, oidc_exchange_failed, or no_inline_comments instead of pasting full logs.
Escalate security privately
If a report could involve leaked credentials, tenant isolation, or workflow secret exposure, do not open a public issue. Email quantjumppro@gmail.com with links and safe error categories first.
Keep these out of tickets and public issues.
- Codex auth.json contents, refresh tokens, API keys, or GitHub tokens
- private source code snippets or full PR diffs
- raw prompts, model output dumps, or logs containing secrets
- GitHub App private keys or webhook secrets