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

Updates to notebook testing automation #342

Merged
merged 23 commits into from
Aug 9, 2024

Merge pull request #1 from HowieG/automate-notebook-testing

3b8e95b
Select commit
Loading
Failed to load commit list.
Merged

Updates to notebook testing automation #342

Merge pull request #1 from HowieG/automate-notebook-testing
3b8e95b
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Aug 9, 2024 in 36s

4 secrets uncovered!

4 secrets were uncovered from the scan of 21 commits in your pull request. ❌

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

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.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #343: main 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
12083425 Triggered Generic High Entropy Secret f0148f1 tests/core_manual_tests/agentchat_agentops.ipynb View secret
12083425 Triggered Generic High Entropy Secret f0148f1 tests/core_manual_tests/agentchat_agentops.ipynb View secret
12083425 Triggered Generic High Entropy Secret 3b8e95b tests/core_manual_tests/agentchat_agentops.ipynb View secret
12083425 Triggered Generic High Entropy Secret 3b8e95b tests/core_manual_tests/agentchat_agentops.ipynb 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.