Skip to content
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

Merged
merged 18 commits into from
Jun 15, 2020
Merged

Add guidelines for PR reviews. #197

merged 18 commits into from
Jun 15, 2020

Conversation

smoia
Copy link
Member

@smoia smoia commented Apr 2, 2020

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

  • Add review guidelines in contributor guide.
  • Minor adjustments related to the adoption of auto

@smoia smoia added Documentation This issue or PR is about the documentation Paused Issue should not be worked on until the resolution of other issues or Pull Requests Community This issue is about the community, not the code labels Apr 2, 2020
@codecov
Copy link

codecov bot commented Apr 2, 2020

Codecov Report

Merging #197 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #197   +/-   ##
=======================================
  Coverage   93.68%   93.68%           
=======================================
  Files           8        8           
  Lines         681      681           
=======================================
  Hits          638      638           
  Misses         43       43           

@RayStick
Copy link
Member

RayStick commented Apr 2, 2020

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.

@vinferrer
Copy link
Collaborator

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

@smoia
Copy link
Member Author

smoia commented Apr 2, 2020

Yes @RayStick , I added a point about it actually! I pushed, but probably while GitHub was down - I'm trying again.

docs/contributorfile.rst Outdated Show resolved Hide resolved
@eurunuela
Copy link
Collaborator

I think this is fine. Thanks @smoia !

docs/contributorfile.rst Outdated Show resolved Hide resolved
@RayStick
Copy link
Member

RayStick commented Apr 3, 2020

Yes @RayStick , I added a point about it actually! I pushed, but probably while GitHub was down - I'm trying again.

I see the change now.
Guidelines are clear and easy to read. :)

@vinferrer
Copy link
Collaborator

looks good to me

@RayStick
Copy link
Member

RayStick commented Apr 10, 2020

@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:

"Use the ‘Reviewer’ option to assign one (or more) people to review the changes you have made. If the ‘Assignee’ option is left blank, the last reviewer to approve the PR should do the final merge. If you don’t want this to be the case, use the ‘Assignee’ option to specify which person you want to merge the new branch into master.

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.

@smoia
Copy link
Member Author

smoia commented Apr 10, 2020

@RayStick yes, I added them in the last commit.
The contributor guidelines document has become huge and probably too complex to be read, if anyone has suggestion on how to improve it, I'd welcome new and fresh ideas!

@RayStick
Copy link
Member

I can read it properly next week, and try to cut it down a bit, if you like.

@smoia
Copy link
Member Author

smoia commented Apr 10, 2020

@RayStick sure, thank you!
I don't know if it's about cutting or about reorganising it, maybe using the other contributor-targetting page, this one

@smoia
Copy link
Member Author

smoia commented May 14, 2020

@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.

@RayStick
Copy link
Member

I will read it today! Anything specific you want feedback on or improved, or is it just a general read for clarity?

@RayStick RayStick requested review from RayStick and removed request for RayStick May 14, 2020 17:24
@smoia smoia marked this pull request as ready for review May 14, 2020 18:36
@smoia
Copy link
Member Author

smoia commented May 14, 2020

I can read it properly next week, and try to cut it down a bit, if you like.

@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!

@eurunuela
Copy link
Collaborator

@smoia, @RayStick it looks like you have some merge conflicts. How close from review do you think this is?

@RayStick
Copy link
Member

I'll resolve them now

@RayStick
Copy link
Member

@eurunuela We are very close to it needing review, but I just want to check a few things with @smoia first.

@RayStick RayStick requested review from RayStick and removed request for RayStick May 15, 2020 19:01
@RayStick
Copy link
Member

@smoia I am making a few more smaller changes, that I will submit to your local branch soon.

@RayStick
Copy link
Member

@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.

@smoia
Copy link
Member Author

smoia commented May 18, 2020

I'm sorry @RayStick , I just missed the PR. @eurunuela do you want to be the main reviewer for this one?

@RayStick
Copy link
Member

No problem @smoia !

@eurunuela
Copy link
Collaborator

I'm sorry @RayStick , I just missed the PR. @eurunuela do you want to be the main reviewer for this one?

Sure, I'll take the lead!

Copy link
Collaborator

@eurunuela eurunuela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for the changes @smoia and @RayStick !

docs/contributorfile.rst Outdated Show resolved Hide resolved
docs/contributorfile.rst Outdated Show resolved Hide resolved
Copy link
Collaborator

@eurunuela eurunuela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for the changes @smoia and @RayStick !

@eurunuela
Copy link
Collaborator

Can you please have a look at this @vinferrer and PR?

@eurunuela
Copy link
Collaborator

Given that this is a documentation change and only one PR is needed, I'll merge if @smoia and @RayStick are happy with it.

@smoia
Copy link
Member Author

smoia commented Jun 1, 2020

I'm puzzled by the loss of coverage 🤔.
In any case, this is a paused PR, since it kind of depends on #181 being merged first.
#181 will be merged as soon as we close #206, #212, #222, #223 - it should happen in two weeks!
If it's accepted, I'll merge it in at the right time. Thank you for keeping an eye on it though!

@eurunuela
Copy link
Collaborator

I didn't know this PR depended on #181 . Good to know!

@smoia smoia merged commit f6fc624 into physiopy:master Jun 15, 2020
@smoia smoia added the released This issue/pull request has been released. label Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community This issue is about the community, not the code Documentation This issue or PR is about the documentation Paused Issue should not be worked on until the resolution of other issues or Pull Requests released This issue/pull request has been released.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants