-
Notifications
You must be signed in to change notification settings - Fork 246
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
Docs overhaul #226
Docs overhaul #226
Conversation
…-AI/agentops into eng-411-docs-overhaul-2
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
10824647 | Triggered | Generic High Entropy Secret | e03df8e | docs/mint.json | View secret |
10824647 | Triggered | Generic High Entropy Secret | e937c85 | docs/mint.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future, can we please keep PRs much much smaller. Even though these changes are all in the same vein, the larger the PR, the more likely stuff gets messed up, confused or lost
@bboynton97 I needed to xlr8 |
@bboynton97 but forreal I did one big PR bc I think it would've taken 3x as long to make branches for each and not have them conflict etc and the corresponding dip in motivation. Felt lower risk than code changes |
@bboynton97 otherwise yes I always try to keep my PRs modular |
Resolves ENG-411