bug iniciar atendimento telegram e sincronização de contatos

[williamcostaramos]

[netlify[bot]]

✅ Deploy Preview for appizing canceled.

Name	Link
🔨 Latest commit	870e3572c93afa48865727899ad1b81211db83c4
🔍 Latest deploy log	https://app.netlify.com/sites/appizing/deploys/64370bf5fbe79d0008a54325

[netlify[bot]]

❌ Deploy Preview for izing failed.

Name	Link
🔨 Latest commit	870e3572c93afa48865727899ad1b81211db83c4
🔍 Latest deploy log	https://app.netlify.com/sites/izing/deploys/64370bf5a357d50008424801

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 3 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
-	Generic High Entropy Secret	8805ca3e2aa3c9a90dd2d9c738705ee14e169d7c	backend/.env.example	View secret
-	Generic High Entropy Secret	8805ca3e2aa3c9a90dd2d9c738705ee14e169d7c	backend/.env.example	View secret
-	Generic High Entropy Secret	8805ca3e2aa3c9a90dd2d9c738705ee14e169d7c	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 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>