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

Mistaken PR #1

Closed

Conversation

orihomie
Copy link

@orihomie orihomie commented Jan 18, 2025

Pls delete this.

@orihomie orihomie closed this Jan 18, 2025
Copy link

gitguardian bot commented Jan 18, 2025

⚠️ GitGuardian has uncovered 2 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic Password 4fb6bf2 docker/db/docker-compose.yml View secret
- - Generic Password 4fb6bf2 docker/db/docker-compose.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.

@orihomie orihomie reopened this Jan 18, 2025
@orihomie orihomie force-pushed the feature/profile-tag-flags branch from f3ee043 to ab336d5 Compare January 18, 2025 12:57
@orihomie orihomie closed this Jan 18, 2025
@orihomie orihomie force-pushed the feature/profile-tag-flags branch from ab336d5 to ea82bfc Compare January 18, 2025 12:58
@orihomie orihomie changed the title Feature/profile tag flags Mistaken PR Jan 18, 2025
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