GabdaSilva07 / Ellis-BackEnd

0 stars 0 forks source link

Configure Sweep #25

Open sweep-ai[bot] opened 1 year ago

sweep-ai[bot] commented 1 year ago

๐ŸŽ‰ Thank you for installing Sweep! We're thrilled to announce the latest update for Sweep, your AI junior developer on GitHub. This PR creates a sweep.yaml config file, allowing you to personalize Sweep's performance according to your project requirements.

What's new?

If you would like me to stop creating this PR, go to issues and say "Sweep: create an empty sweep.yaml file". Thank you for using Sweep! ๐Ÿงน

gitguardian[bot] commented 1 year ago

โš ๏ธ 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 | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [8224621](https://dashboard.gitguardian.com/incidents/8224621?occurrence=115727376) | Google Cloud Keys | 28597875c0f26e73afd2635648e3cd6a767b91ae | EllisFitnessApp/FirebaseService/firebase.json | [View secret](https://github.com/GabdaSilva07/Ellis-BackEnd/commit/28597875c0f26e73afd2635648e3cd6a767b91ae#diff-c4f101b59bcc3c28208393bc93b416553d0d231b8fb8debe94abf8813d2b8e03R5) |
๐Ÿ›  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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/detectors/specifics/googlecloud#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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 - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

๐Ÿฆ‰ 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!