-
Notifications
You must be signed in to change notification settings - Fork 56
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
Dependency and workflow updates #256
Conversation
BrandtH22
commented
Jan 11, 2024
- replaces yarn with npm in deployment
- adds review deployment and deletion
- updates runnable import to referential path rather than absolute for ease of translation integrations
- adds trailing slash for seo
- adds Chia Docs to the header
- updates all dependencies, imports, and readme for running
- updates all dependencies, imports, and readme for running
- adds trailing slash for seo - adds Chia Docs to the header
- updates runnable import to referential path rather than absolute for ease of translation integrations
- replaces yarn with npm in deployment - adds review deployment and deletion
flips the npm install and npm ci commands
add k8s files
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: @docusaurus/[email protected], [email protected], [email protected] |
fixes for the docker file and inclusion of cname
updates to domains used in review deploy workflow
adds the create cert namespace to negate exit 1
fixes the domain listed in the cert
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.
My approval is for the CI/Docker/K8s manifest portions of the diff. I would gather additional reviewer(s) for the docs content where applicable. If future changes to docs content dismiss my review, that's fine. Just wanted to document my approval of that portion since github doesn't have a foolproof method of split approvals for PRs that do multiple things.
removes the yarn packages and package-lock json from the gitignore
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.
Looks good to me on the docs side of things