-
Notifications
You must be signed in to change notification settings - Fork 4
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
chore: move common components to a lib for sharing #886
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
10261144 | Triggered | Generic High Entropy Secret | 89305e4 | packages/ui/components/package.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 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.
"main": "src/index.ts", | ||
"sideEffects": [ | ||
"*.css", | ||
"*.scss" |
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.
nice!
…2-f1434d82021ab.mjs
Short description of the changes made
Moves the simplest components over to a
@fern-ui/components
lib to share with the other FEs (specifically the releases UI)What was the motivation & context behind this PR?
The releases UI shouldn't depend on the docs FE, so moving base components to a sharable location that is JUST components
How has this PR been tested?
Not YET ;)