Open dgcrouse opened 7 years ago
Same as #184. It's not the PR author's fault if their code hasn't been reviewed, or now has merge conflicts. Rejecting PRs without good reason leaves a bad taste.
As for merging PRs, just do the usual. Make sure the code's been tested and reviewed, and if in doubt, err on the side of caution by tagging people to weigh in.
Works for me.
We need a standard to review any PRs that come through, any suggestions?
I also move to reject all PRs in the backlog and encourage writers to resubmit. That way we can sort out what is actively being worked on and lessen the load.