Re: [hibernate-dev] Relaxing the pull request review requirement

At least in HV we've been doing this effectively already, e.g. fixed typos without creating a PR. In particular when doing a review of a PR, merging this and adding another commit with this sort of tiny fixes, without creating a new PR for this. So I think this makes sense in some situtations, but IMO it really should be a very rarely used exception. Otherwise there might be the danger that the limit of what is considered small enough to self-merge slowly rises of time. I think the root question really is why do peer reviews lead to "painfully slow integrations". Are you regularly waiting for your PRs to be integrated? Then maybe the possible reviewers should make it a higher prio to do the reviews? Personally, I try to do any PR reviews with a very high prio, i.e. bring my current task to a state where I can do a task change and do the review. is simple enough, the review done by the bot should be considered good enough. What kind of "review" is the bot doing in addition to running the build? --Gunnar 2013/5/1 Sanne Grinovero <sanne(a)hibernate.org&gt;