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
Document code-review practices #93
Conversation
This is by no means complete or comprehensive, but it is a start! Feel free to comment here on this PR, or open issues for ways to improve 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.
Woooooo this was a great addition! Can I copy paste it to z2jh later? We have a lot of work to do regarding testing there still though =)
I'm picking up a lot of wisdom and knowledge from you @yuvipanda thank you =D ❤️
|
||
We recommend reading `On Empathy & Pull Requests <https://slack.engineering/on-empathy-pull-requests-979e4257d158>`_ | ||
and `How about code reviews <https://slack.engineering/how-about-code-reviews-2695fb10d034>`_ | ||
to learn more about being empathetic in code reviews. |
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.
Looking forward to read these articles!
- [ ] Add / update documentation | ||
- [ ] Add tests | ||
|
||
<!-- Read more about our code-review guidelines at https://the-littlest-jupyterhub.readthedocs.io/en/latest/contributing/code-review.html --> |
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.
I've seen a lot of templates, I think this is perfect - useful and easy.
Also add a pull request template