Bug: Issue auto-closes when password or secret detected by security automation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the attached publish-workspace.yml and the repository's bots, actions, secret-scanning, and other automation rules. Reproduce the behavior with a security-related issue description, identify which automation closes or blocks it, and document a way to report genuine concerns without false positives.
Written by the indexing model from the issue text.
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
- Dominant language
- PLpgSQL
- Stars
- 275
- Forks
- 102
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/splinter
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
documentation
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in supabase/splinter
Similar issues
-
kind/bug Ubuntu 24
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kubernetes-sigs/kubespray#13532 ·
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elementary/flatpak-platform#253 ·
-
tagbot-manual
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100