-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
convert glossary html to md (4) #7588
Conversation
Preview URLs
FlawsNote! 7 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLsURL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL: No new external URLs URL:
URL: No new external URLs URL:
URL:
URL:
URL:
URL: No new external URLs |
@hochan222 if you want you can use the "Markdown conversion" milestone in the metadata for those PR |
@SphinxKnight Thank you for telling me :) I tried to deal with things that can be completed in a short period of time quickly, and then register and manage large-scale learn or web as milestones as an issue. If I upload a PR to Milestone, I think it will be complicated to track other issues, so I'm only going to register an issue. What do you think? Any other recommendations? |
It is managed at the bottom here, but it seems like a good way to make it in advance for other people in the future. |
Yes you're right :) I'll remove the PRs I put there. Tracking with a global issue per locale seems the right "balance" |
Yes, I understand. I will proceed in the same way. Thank you.🙇 |
IMO adding PRs to the milestone is alright, it's up to you all whether to do so! I personally like the idea of adding these PRs to the milestone since their merge will increase the completion progress of the milestone. :D |
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.
In regards to the PR itself, LGTM after a quick skimming of the files!
convert glossary html to md