Skip to content

Conversation

@jbonofre
Copy link
Member

@jbonofre jbonofre commented Jan 5, 2026

No description provided.

Copy link
Contributor

@evindj evindj left a comment

Choose a reason for hiding this comment

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

as per agreement in the discussion thread.

@github-project-automation github-project-automation bot moved this from PRs In Progress to Ready to merge in Basic Kanban Board Jan 7, 2026
Copy link
Contributor

@singhpk234 singhpk234 left a comment

Choose a reason for hiding this comment

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

I think this is unfortunate but this is must required now specially
after repeated occurence :
1/ #3207 (comment)
2/#3268 (comment)

@jbonofre
Copy link
Member Author

@flyrain no objection from you about this one ? It seems we have already a consensus from several contributors.

@flyrain
Copy link
Contributor

flyrain commented Jan 21, 2026

To carry on my thoughts on the dev mailing discussion, I don't think enforcing 2 reviewers on PRs solves the problem, meanwhile it can slow down the review process, esp. on trivial PRs. But I will not block it if people want to give it a try.

@jbonofre
Copy link
Member Author

@flyrain I got your point. I'm not hard pushing for this one, but more as an attempt to involve more reviewers.

@adutra @MonkeyCanCode @singhpk234 @dimas-b @evindj @adam-christian-software what do you guys think ? Should we try this ?

I'm fine to close this PR if you think it won't help (I'm not very convinced either 😄 ).

@snazy
Copy link
Member

snazy commented Jan 21, 2026

(Casting my objection on the dev-ML discussion here:)
Not really a fan of having a hard technical requirement of two approvals for every little PR.

@jbonofre
Copy link
Member Author

OK, so, we don't have consensus. Let's close this one, we can revisit later if needed.

@jbonofre jbonofre closed this Jan 21, 2026
@github-project-automation github-project-automation bot moved this from Ready to merge to Done in Basic Kanban Board Jan 21, 2026
@adutra
Copy link
Contributor

adutra commented Jan 21, 2026

For posterity I'm with @flyrain here: I don't really think 2 reviewers solves the original issue, but I wouldn't oppose the idea either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants