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

Cleanup, renaming and refactoring #81

Merged
merged 11 commits into from
Feb 11, 2025
Merged

Cleanup, renaming and refactoring #81

merged 11 commits into from
Feb 11, 2025

Conversation

ajosh0504
Copy link
Collaborator

This notebook does the following:

  • Updates notebooks with appname devrel.content.python -> something specific
  • Adds READMEs to all folders
  • Moves/renames low-impact folders
  • Cleans up the main README to keep it succinct

@ajosh0504 ajosh0504 requested a review from a team as a code owner February 5, 2025 19:58
Copy link

gitguardian bot commented Feb 10, 2025

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
15555450 Triggered Generic Password ff02a31 notebooks/benchmarks/vector_database_comparison_mongodb_postgreSQL.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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  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.

@ajosh0504 ajosh0504 merged commit 61d0b06 into main Feb 11, 2025
1 of 2 checks passed
@ajosh0504 ajosh0504 deleted the cleanup branch February 11, 2025 18:01
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.

2 participants