Bug: Issue auto-closes when password or secret detected by security automation #138
Description
Describe the bug
When submitting issues in the supabase/splinter repository, they are automatically closed or blocked if the text contains references that are flagged as passwords or secrets—even if no credential is actually exposed. This prevents me from keeping my security-related issues open for review. This might be due to automated bots, GitHub secret scanning, GitGuardian, or repository-specific workflow rules.
To Reproduce
- Open a new issue and describe a concern involving passwords or secrets.
- Observe that the issue closes automatically or is blocked from submission.
Expected behavior
Issues regarding security concerns should not be auto-closed unless a real, exposed secret is detected. Accurate reporting should be possible without triggering false positives.
Additional context
- Please review repository automation (bots, actions, scanners) for strict secret detection and provide guidelines to avoid false positives.
- publish-workspace.yml