-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
migrate frontend to docusaurus #9014
Changes from 35 commits
34bdb6d
b293065
20aea04
e6f9b0d
1cc9572
b8cb4d8
abf4bd4
87f5b97
d27370f
2d5fd7f
ece6472
77b0343
235d2b0
1ecf949
956d617
ef74cbb
3fe9470
65881f1
e0004d5
d659e91
c99fdb2
b38bd85
df46828
f1243e3
19a2080
2931df6
2e2ee69
3adb7bd
1cd61cd
424c411
25aab60
fbf50a9
bd43d07
c4288f6
2accfd2
b2ff593
ab3785b
5d6ff7e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -107,7 +107,7 @@ You can read a [tutorial on how to add a badge][tutorial]. | |
|
||
When server source files change, the badge server should automatically restart | ||
itself (using [nodemon][]). When the frontend files change, the frontend dev | ||
server (`gatsby dev`) should also automatically reload. However the badge | ||
server (`docusaurus start`) should also automatically reload. However the badge | ||
definitions are built only before the server first starts. To regenerate those, | ||
either run `npm run defs` or manually restart the server. | ||
Comment on lines
+110
to
112
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Depending on what we decide when it comes to #9014 (comment) we might need to update this and also https://github.com/badges/shields/blob/master/doc/TUTORIAL.md?plain=1#L305 |
||
|
||
|
This file was deleted.
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.
If you already have a checkout of shields, these removed paths will become unstaged files in your checkout after pulling this. Other than "just live with it", is there any good pattern for dealing with this?
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.
not that i know of. it's something i've experienced occasionally in a few projects, and always just dealt with via local cleanups (either via git or just standard file system management tooling).
i do not think this is worth the effort, especially given our current quantity of regular contributors, but the only potential automated/assistive route i can think of would be seeing if there's any git client hooks (post-merge maybe?) we could hook into (pun very much intended) that would deal with any such known files/directories for our project