Skip to content

FIX: Implement Advanced SEO Enhancements and Google Search Readiness (#75)#79

Open
ayyushh-18 wants to merge 18 commits into
daviddprtma:mainfrom
ayyushh-18:main
Open

FIX: Implement Advanced SEO Enhancements and Google Search Readiness (#75)#79
ayyushh-18 wants to merge 18 commits into
daviddprtma:mainfrom
ayyushh-18:main

Merge branch 'main' into main

8c20870
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Jun 16, 2026 in 38s

1 secret uncovered!

1 secret were uncovered from the scan of 18 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #79: main 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
22500435 Triggered Supabase Service Role JWT ce13c6f backend/.env.example View secret

🛠 Guidelines to remediate hardcoded secrets

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.