-
Notifications
You must be signed in to change notification settings - Fork 441
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
Merge duplicate CONTRIBUTING contents #2110
Conversation
Thanks for tackling this @tkoyama010 (and for noticing the issue in the first place). I think most contributors would be reading the online docs version, so we should definitely have an rst rendered there. The question is whether we just use a stub I can't tell which one is better, personally. |
Having seen the discussion at #2105, I think it is better to follow the authors.rst example as @banesullivan said.
The rst file can be checked on GitHub without any problem, so I think it is fine to turn markdown into rst. |
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.
Thanks @tkoyama010! Agree with using rst as we can avoid duplication.
Overview
We have deplicate contents in CONTRIBUTING.md and Contributing. It is not good that we have to write same thing in 2 places. I merge the content and save it to
CONTRIBUTING.mdCONTRIBUTING.rst.Details
resolve #2105