Create infisical-secrets-check.yml

[guibranco]

Resolves #ISSUE_NUMBER

---

Before the change?

After the change?

Pull request checklist

• Tests for the changes have been added (for bug fixes/features)
• Docs have been reviewed and added/updated if needed (for bug fixes/features)

Does this introduce a breaking change?

• Yes
• No

---

[deepsource-io]

Here's the code health analysis summary for commits 05005b9..dee1ea4. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
SQL	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
PHP	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Php
Branch Coverage	100%	100%
Composite Coverage	33.3%	33.3%
Line Coverage	33.3%	33.3%

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

Scan results:

�[90m11:48PM�[0m �[32mINF�[0m scanning for exposed secrets...
�[90m11:48PM�[0m �[32mINF�[0m 41 commits scanned.
�[90m11:48PM�[0m �[32mINF�[0m scan completed in 267ms
�[90m11:48PM�[0m �[32mINF�[0m no leaks found

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

🔍 Lint summary

✅ Lint check passed.