Master

[BTheCoderr]

No description provided.

[vercel]

Deployment failed with the following error:

Environment Variable "NEXT_PUBLIC_CLOUDINARY_CLOUD_NAME" references Secret "cloudinary_cloud_name", which does not exist.

[netlify]

❌ Deploy Preview for jackerbox failed. Why did it fail? →

Name	Link
🔨 Latest commit	7f836c7
🔍 Latest deploy log	https://app.netlify.com/sites/jackerbox/deploys/681f71bbfc4d86000803ae68

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
16809822	Triggered	Generic Database Assignment	bf91b39	quick-test.js	View secret
16809823	Triggered	PostgreSQL Credentials	bf91b39	pg-test.js	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}