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

refactor: migrate live quiz to unified data structure (i.e., from question instances/blocks to element block and element instances) #4338

Merged
merged 38 commits into from
Nov 30, 2024

fix(packages/graphql): await instance migrations in redis migration s…

c4e050f
Select commit
Loading
Failed to load commit list.
Merged

refactor: migrate live quiz to unified data structure (i.e., from question instances/blocks to element block and element instances) #4338

fix(packages/graphql): await instance migrations in redis migration s…
c4e050f
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Nov 30, 2024 in 3s

8 secrets uncovered!

8 secrets were uncovered from the scan of 38 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #4338: v3-new-live-quiz 👉 v3
GitGuardian id GitGuardian status Secret Commit Filename
1509424 Triggered Generic Password 761360a docker-compose.yml View secret
1509424 Triggered Generic Password 761360a deploy/compose/docker-compose.yml View secret
1623504 Triggered Username Password 761360a deploy/compose-traefik-proxy/klicker/services.env View secret
1509424 Triggered Generic Password 761360a deploy/compose/docker-compose.yml View secret
1509424 Triggered Generic Password c06d004 util/_restore-db.sh View secret
1509424 Triggered Generic Password c06d004 util/_restore-db.sh View secret
1509424 Triggered Generic Password c06d004 docker-compose.yml View secret
1509424 Triggered Generic Password c06d004 util/_restore-db.sh 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.