-
Notifications
You must be signed in to change notification settings - Fork 39
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
Lint and format docs #136
Lint and format docs #136
Conversation
893c05b
to
f1e735b
Compare
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.
Can you edit the commit message from Re-push updates with signed commits
to something descriptive of the change itself, e.g. Add docs linting/fixing
.
f1e735b
to
bf84f18
Compare
Signed-off-by: Pavithra Eswaramoorthy <pavithraes@outlook.com>
Signed-off-by: Pavithra Eswaramoorthy <pavithraes@outlook.com>
bf84f18
to
52e3fa0
Compare
Thanks for the review, I've made the necessary updates :) |
It doesn’t exist already but it might be nice to have a linting subsection in the dev guide, explaining what is linted with what tools and with a pointer toward |
We can add more to the existing lint and fix section |
Oops, forgot that was in the build instructions. |
Also the contributing guidelines should be moved to the 99 developer page as they include required information (like e.g. closing PRs with non-substantive changes or without prior discussion for big features). But we can do in a followup PR to avoid conflicts |
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.
3 followup changes:
- Add these 2 new deps to conda yaml
- Move contributing guidelines from 98 to 99
- Expand 98 linting/fixing docs and link from 99
…ests/acceptable contributions from 98 to 99, add docs linting section to 98 Signed-off-by: Tim Paine <timothy.paine@cubistsystematic.com>
Fixes #135