Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development to Main #2

Merged
merged 73 commits into from
Mar 3, 2024
Merged

Development to Main #2

merged 73 commits into from
Mar 3, 2024

Conversation

fabianoflorentino
Copy link
Owner

No description provided.

Copy link

gitguardian bot commented Mar 3, 2024

⚠️ GitGuardian has uncovered 11 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
9725922 Triggered Generic Password 02ec2c7 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 02ec2c7 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 6f10d05 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password f18917d .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 20faf50 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 20faf50 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 20faf50 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 4732b33 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password 4732b33 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password b918df5 .github/workflows/unit_tests.yml View secret
9725922 Triggered Generic Password b918df5 .github/workflows/unit_tests.yml 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


🦉 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!

@fabianoflorentino fabianoflorentino marked this pull request as ready for review March 3, 2024 16:34
@fabianoflorentino fabianoflorentino merged commit e209e7a into main Mar 3, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant