Stage

[evereq]

PR

• Have you followed the contributing guidelines?
• Have you explained what your changes do, and why they add value?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

---

[gitguardian]

⚠️ GitGuardian has uncovered 8 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	Secret	Commit	Filename
7421875	Google API Key	a029701	.deploy/k8s/k8s-manifest.civo.prod.yaml	View secret
7421875	Google API Key	e913ac3	.deploy/k8s/k8s-manifest.civo.prod.yaml	View secret
7421875	Google API Key	e913ac3	.deploy/k8s/k8s-manifest.civo.stage.yaml	View secret
7421875	Google API Key	a029701	.deploy/k8s/k8s-manifest.civo.stage.yaml	View secret
7421875	Google API Key	b3de071	.deploy/k8s/k8s-manifest.civo.stage.yaml	View secret
7421875	Google API Key	b3de071	.deploy/k8s/k8s-manifest.civo.prod.yaml	View secret
7421875	Google API Key	d09325e	.deploy/k8s/k8s-manifest.civo.stage.yaml	View secret
7421875	Google API Key	d09325e	.deploy/k8s/k8s-manifest.civo.prod.yaml	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
5 out of 6 committers have signed the CLA.

✅ adkif
✅ rahul-rocket
✅ coderNadir
✅ Gramosx
✅ evereq
❌ BM-Nadir

---

BM-Nadir seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 866dabf. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

🟥 Failed Commands
nx serve api -c=production --prod

---

Sent with 💌 from NxCloud.