-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add reference to ReviewNB to Code Review section. #247
Conversation
best_practices/code_review.md
Outdated
You can use [ReviewNB](https://www.reviewnb.com/) for that. If you configure | ||
your esciencecenter.nl email address as your primary email for your Github | ||
account [here](https://github.com/settings/emails) you have access to the | ||
academic plan with full benefits. |
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 am not sure if we should add the 2nd part about the academic plan. It is nice to know for escience center staff, but it is ofcourse not a generally applicable best practice.
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.
The NLeSC guide should be targeted at NLeSC staff. All generic stuff should be in The Turing Way instead. So it's okay to suggest NLeSC specific things.
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.
Check!
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.
Couple of minor suggestions that I think would make the section more readable as a new comer.
Co-authored-by: Carlos Martinez <c.martinez@esciencecenter.nl>
Co-authored-by: Carlos Martinez <c.martinez@esciencecenter.nl>
@jmaassen or @c-martinez. Sorry I lost track of this... This can be merged now! |
Thanks @svenvanderburg ! |
Add reference to reviewing jupypter notebooks with ReviewNB to Code Review section.