We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
在艰苦的环境下(指 GitHub 对 Markdown 的渲染),写出清晰易懂的 README!
(注:尽量 简略 列出有关课程的 所有 内容) (长期工作,缓慢进行……) (README 意见专用 issue)
The text was updated successfully, but these errors were encountered:
@skyleaworlder Basically, I think a good readme is to go tidy and simple. Apparently, it was made a bit chaotic...
I would recommend we adhere to the following structure:
Sorry, something went wrong.
@skyleaworlder Basically, I think a good readme is to go tidy and simple. Apparently, it was made a bit chaotic... I would recommend we adhere to the following structure: an introduction telling why we are here. a table of content (免责)声明
说得对啊!这个暑假有重写大部分 README 的计划,到时候会仔细考虑该建议的!
skyleaworlder
No branches or pull requests
在艰苦的环境下(指 GitHub 对 Markdown 的渲染),写出清晰易懂的 README!
各课程的总 README 规范如下:
(注:尽量 简略 列出有关课程的 所有 内容)
(长期工作,缓慢进行……)
(README 意见专用 issue)
The text was updated successfully, but these errors were encountered: