Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11016360 | Triggered | Generic Password | dc73532 | app/.github/workflows/test-api.yaml | 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.
|
As per the documentation - not able to find below https://github.com/AgentOps-AI/agentops/blob/main/app/README.md git clone https://github.com/AgentOps-AI/AgentOps.Next.git
|
Hey @himanshudubey01 -- the |
|
Hey team, we were trying to self host agentops as per your recent release and we are facing issues with the process, I think the documentation has some gaps can you please confirm if this matches the repo - # 1. Clone the repository 2. Copy environment filescp .env.example .env 3. Configure external services (see guides below)Edit .env files with your service credentials4. Start with Dockerdocker-compose up -d |


📥 Pull Request
📘 Description
Briefly describe the changes you've made.
🧪 Testing
Describe the tests you performed to validate your changes.