-
Notifications
You must be signed in to change notification settings - Fork 45
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 guidelines for PR reviews. #197
Conversation
Codecov Report
@@ Coverage Diff @@
## master #197 +/- ##
=======================================
Coverage 93.68% 93.68%
=======================================
Files 8 8
Lines 681 681
=======================================
Hits 638 638
Misses 43 43 |
I gave it a read and it looks good to me. At the moment, I have one question relating to reviewing and merging PRs: If I am the last reviewer to approve a PR, but travis still says "some checks haven't been completed yet" I assume I should wait until I merge? Even if the branch has no conflicts with base branch? If so, we should make this clearer in the contributor file. |
Yes you should always wait for the travis test to finish, because if the test fails you may be merging a PR that is breaking the code |
Yes @RayStick , I added a point about it actually! I pushed, but probably while GitHub was down - I'm trying again. |
I think this is fine. Thanks @smoia ! |
I see the change now. |
looks good to me |
@smoia - so are we going with what I suggested in the meeting, that the assignee slot means that person is responsible for checking it gets done, and then doing the final merge? For the workflow in our lab, I went for these guidelines:
If we want something similar, we should add some text explaining this in the docs, and I can suggest some. But if anyone has different thoughts on that, let me know. |
@RayStick yes, I added them in the last commit. |
I can read it properly next week, and try to cut it down a bit, if you like. |
@RayStick I'm leaving this as a Draft due to your proposal of rewriting it. Would you have time to do so soon? If not, I'm going to graduate it to PR ready for review and if it's accepted we'll merge it in as it is - we can always work on it at another moment. |
I will read it today! Anything specific you want feedback on or improved, or is it just a general read for clarity? |
@RayStick I was referring to this post. It's not necessary short term though! If you think that the documentation is clear and can be merged as is, don't worry about it - just merge it in and we'll think about how to reorganise it at a later time! |
I'll resolve them now |
@eurunuela We are very close to it needing review, but I just want to check a few things with @smoia first. |
@smoia I am making a few more smaller changes, that I will submit to your local branch soon. |
@smoia let me know if anything is unclear with my most recent changes to these documents. After they've been looked at, then it is ready for review by others. |
Text Re-arrangement
I'm sorry @RayStick , I just missed the PR. @eurunuela do you want to be the main reviewer for this one? |
No problem @smoia ! |
Sure, I'll take the lead! |
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.
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 please have a look at this @vinferrer and PR? |
I'm puzzled by the loss of coverage 🤔. |
I didn't know this PR depended on #181 . Good to know! |
Closes nothing, but follows #181
I tried to write down some guidelines for PR reviewers (and update those for PR authors), as that process could follow guidelines too.
Before even reviewing it, I'd like @rmarkello @eurunuela @vinferrer @RayStick and the rest of the team to throw in more suggestions and discuss these guidelines.
Proposed Changes
auto