Closed jhdalek55 closed 3 years ago
This should be merged into Master and not Patch 3. I cant't seem to figure out how to do this.
I'm ready to have this looked at now.
@pattivacek your input is welcomed as well.
Oh, hmm, we should set some branch protection settings here, such as requiring >= 2 reviews. Anyone object?
Oh, hmm, we should set some branch protection settings here, such as requiring >= 2 reviews. Anyone object?
I think it's just because it's currently set to merge into another branch. The main branch is protected. @jhdalek55 there should be an Edit button near the top of this PR for you and from there you can change the branch being merged into.
As far as the text, I think this is pretty far outside of my base of knowledge to comment meaningfully.
@trishankatdatadog you are probably right that we should mandate two reviews here as we do on the Standard. I have no objections to changing this. We may need to look into how we assign reviews though. Too often pull requests sit unmerged for a long time not because of legitimate debate on its merits, but just because the author can't even get one review.
@trishankatdatadog you are probably right that we should mandate two reviews here as we do on the Standard. I have no objections to changing this. We may need to look into how we assign reviews though. Too often pull requests sit unmerged for a long time not because of legitimate debate on its merits, but just because the author can't even get one review.
I feel your pain, and such is the nature of open source work 😢 Perhaps the best we can do is to remind people at meetings.
This PR partially addresses Standard Issue #162.
Can we get one more review to close this out?
Ok, Patti, I've followed up on your comments. If you can approve this, I can merge.
Good eyes. Are we good to go now?
I've gotten two approvals, so I am going to close this one out. Thanks.
This is still a bit rough. Feel free to make suggestions or amend this PR, but don't merge as of yet