security: add gitleaks secret scanning CI workflow#300
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Open
Adds .github/workflows/secret-scan.yml to detect hardcoded secrets on every push/PR to main using gitleaks/gitleaks-action@v2. Adds .gitleaks.toml allowlist to suppress false positives from test fixtures and .env.example files. The leaked Telegram token in the issue was NOT present in the codebase; it only appeared in the GitHub issue text and must be revoked via BotFather. Agent-Logs-Url: https://github.com/Tryonme-com/tryonyou-app/sessions/0a89b63e-d6b9-41d0-9cd1-56ad094f1e57 Co-authored-by: LVT-ENG <[email protected]>
Copilot
AI
changed the title
[WIP] Add API token to .env file for bot configuration
security: add gitleaks secret scanning CI workflow
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A Telegram bot token was leaked in a GitHub issue. The token was not hardcoded in the codebase (all Telegram credentials already use
os.environ), but no CI gate existed to catch future accidental commits of secrets.Changes
.github/workflows/secret-scan.yml— New workflow runninggitleaks/gitleaks-action@v2on every push/PR tomain. Fails the build if any hardcoded credential is detected..gitleaks.toml— Allowlist config to suppress false positives:tests/— uses obviously fake keys (sk_test_fake123,sk_live_test, etc.)*.env.examplefiles — document variable names only, no real valuesAction required (out of band)
The exposed token
8788913760:AAE2g87I0eGtlydPlkXYeABBPrbu3eDeb7kwas published publicly in the issue and must be revoked via@BotFather→/revokeregardless of this PR.