-
Notifications
You must be signed in to change notification settings - Fork 308
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
feat: Cookbook Onboard (AI Assistant & Playground) #1387
feat: Cookbook Onboard (AI Assistant & Playground) #1387
Conversation
✅ Deploy Preview for celo-docs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
- | - | Generic High Entropy Secret | 438b7cc | src/theme/Navbar/index.js | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
1283f78
to
438b7cc
Compare
Thank you for the initiative! Does Celo need to pay for this service? If yes, please provide pricing plans. If no, please provide details on any limits (like no. of queries etc...) Can you also please explain if the chatbot will have information about any new pages we add to the docs automatically or is there a process for the same? |
Thank you for getting back to us! Right now, we're focused on growth and helping blockchains like Celo reduce developer onboarding friction within their ecosystems. Our goal is to enhance the effectiveness of our developer relations team, which is why we haven't set any pricing plans or limits for this version of Cookbook Onboard. While some blockchain networks choose to support Cookbook’s free initiatives, such as this version of Cookbook Onboard, through token grants, there's no obligation for them to do so for us to make it available. Regarding data population, we provide your team with access to our CMS, where you can configure the resources the bot uses to reply. By default, they are updated every 24 hours, but you can also refresh them manually when necessary :) |
@therealharpaljadeja, are there any other questions or concerns we can address to get this merged? :) |
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.
Reviewed IRL with michael
@ClockRide a secret exposed in https://github.com/celo-org/docs/pull/1387/checks?check_run_id=28141879962 |
Yep! |
Resolves #1386