merge

[paulorosadodev]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 9 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
11480827	Triggered	Generic Password	93cf18a	test_initiate.py	View secret
11480827	Triggered	Generic Password	a245234	test_initiate.py	View secret
11480827	Triggered	Generic Password	fbf5414	test_initiate.py	View secret
11480827	Triggered	Generic Password	5d01daa	test_initiate.py	View secret
11025028	Triggered	SMTP credentials	1e93823	.env	View secret
11025028	Triggered	SMTP credentials	a245234	.env	View secret
11025028	Triggered	SMTP credentials	298a299	.env	View secret
11025028	Triggered	SMTP credentials	f93df8d	.env	View secret
11599358	Triggered	Generic Password	6065621	cypress/support/commands.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.}