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

Discussion: merge right and responsibility #403

Open
CyFeng16 opened this issue Oct 31, 2019 · 8 comments
Open

Discussion: merge right and responsibility #403

CyFeng16 opened this issue Oct 31, 2019 · 8 comments
Labels
enhancement New feature or request

Comments

@CyFeng16
Copy link
Contributor

@hwfan What about we discussing the right and responsibility when dealing with merging PR? Then we can update the manuals and help improve the process.

@hwfan
Copy link
Contributor

hwfan commented Oct 31, 2019

My idea is that the first reviewer comes is responsible for the whole process of merging. Other reviewers can comment as a supplement.(In order to avoid the mess of multi-processing)

@huan
Copy link
Contributor

huan commented Oct 31, 2019

How about we change the rule to:

  1. Every PR needs two approvements before it is able to be merged.
  2. The second approver takes the responsibility to merge the PR.

Just my two cents, FYI.

@CyFeng16
Copy link
Contributor Author

Two-step reviewing sounds good to me.

@CyFeng16
Copy link
Contributor Author

CyFeng16 commented Nov 1, 2019

@huan Could you please help modify the rules as you mentioned? Close this issue after you have modified the rules. Thanks a lot! 🎉

@CyFeng16 CyFeng16 added the enhancement New feature or request label Nov 1, 2019
@huan
Copy link
Contributor

huan commented Nov 2, 2019

@CyFeng16 It's just my suggestion.

I'd like to make it a discussing topic at one of our seminars, and write it in the meeting notes before we actually modify it.

Because I think it will be better than we modify it directly, how do you think?

@CyFeng16
Copy link
Contributor Author

CyFeng16 commented Nov 2, 2019

@huan We are on the same page. I will submit a proposal at the next meeting.

@CyFeng16
Copy link
Contributor Author

CyFeng16 commented Nov 2, 2019

BTW, voting for issues is really an essential feature.

@CyFeng16
Copy link
Contributor Author

CyFeng16 commented Nov 5, 2019

@hwfan Have you got any conclusions on this issue at your last meeting(#406 )?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants