-
Notifications
You must be signed in to change notification settings - Fork 51
Docs edits #597
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
base: docs-edits
Are you sure you want to change the base?
Docs edits #597
Conversation
Cloudflare pages deployment
Catch up to opentensor repo
Reverting migration things I broke
catchup to opentensor repo state
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -11,6 +11,9 @@ docs/.obsidian | |||
.docusaurus | |||
.cache-loader | |||
.yarnclean | |||
.yarn |
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.
These (L14-L16) were auto-generated files created after I ran yarn install
. You mentioned earlier about the yarn.lock
file being fragile, so I added these files to the gitignore file to avoid any accidents.
package-lock.json
Outdated
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.
Deleted this since it is usually created by an npm install
and we recommend using yarn
in the docs README.
Wanted to avoid a situation where someone unknowingly serves the docs using npm
to avoid any errors.
package.json
Outdated
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 like the item was just moved around a bit. noticed it after the yarn install
PR containing changes from the previous repo, as well as changes over the last couple of days.