storm-software / reaper

💀 A repository containing trading infrastructure, libraries, and applications used by Storm Software
https://reaper.rs
1 stars 1 forks source link

feat(nx-cloud): setup nx workspace #15

Closed sullivanpj closed 2 months ago

sullivanpj commented 2 months ago

feat(nx-cloud): setup nx cloud workspace

This commit set up Nx Cloud for your Nx workspace enabling distributed caching and GitHub integration for fast CI and improved Developer Experience.

You can access your Nx Cloud workspace by going to https://cloud.nx.app/orgs/669ab0a0023e8d3fb6cbc8ef/workspaces/66d04891be451032cd1eeb4c

Note: This commit attempts to maintain formatting of the nx.json, however you may need to correct formatting by running an nx format command and committing the changes.

gitguardian[bot] commented 2 months 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 | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [13590695](https://dashboard.gitguardian.com/workspace/394000/incidents/13590695?occurrence=164138644) | Triggered | Nx Cloud Token | e8fbf2461abaf79d830d36956b8f4e34b56958f5 | nx.json | [View secret](https://github.com/storm-software/reaper/commit/e8fbf2461abaf79d830d36956b8f4e34b56958f5#diff-15552e50b1b7c05b05b7ffe08ee47b5ed62b8d2039229c58972a42fd22a7381cR32) |
🛠 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/secrets-detection-engine/detectors/specifics/nx_cloud_token#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.