Add BypassPullRequestAllowances field

[Starttoaster]

Closes #2431

[codecov]

Codecov Report

Merging #2432 (27efd09) into master (aff6c4b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2432   +/-   ##
=======================================
  Coverage   98.06%   98.06%           
=======================================
  Files         120      120           
  Lines       10558    10558           
=======================================
  Hits        10354    10354           
  Misses        140      140           
  Partials       64       64           

Impacted Files	Coverage Δ
github/repos.go	98.66% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[gmlewis]

Thank you, @Starttoaster !
Just a few minor changes, please.

[Starttoaster]

Thanks for the review @gmlewis ! Committed all suggestions.

[gmlewis]

Thank you, @Starttoaster !
LGTM.

Awaiting second LGTM from any other contributor to this repo before merging.

[Starttoaster]

Thank you, @Starttoaster ! LGTM.

Awaiting second LGTM from any other contributor to this repo before merging.

Thanks!

[gmlewis]

Whups, I jumped the gun... it looks like some of your contributed files need to be run through gofmt, please.

[Starttoaster]

Whups, I jumped the gun... it looks like some of your contributed files need to be run through gofmt, please.

Weird. Usually my text editor fmts for me, I guess it didn't because of the length of the file. Thanks!

[Starttoaster]

@gmlewis pardon me if this comes off as hasty, I just kind of want to switch my go.mods off of my fork, and open up this PR to see if it's merged once a day or so. I was curious what the usual expectation is for duration of time between first and second tier of PR reviews? Not trying to put pressure, I just want to set my expectations accordingly.

[gmlewis]

@gmlewis pardon me if this comes off as hasty, I just kind of want to switch my go.mods off of my fork, and open up this PR to see if it's merged once a day or so. I was curious what the usual expectation is for duration of time between first and second tier of PR reviews? Not trying to put pressure, I just want to set my expectations accordingly.

Hi @Starttoaster - this repo is maintained by volunteers and we rely on other contributors to the repo to perform second code reviews when appropriate. Sometimes it is immediate, but more often it takes days or weeks. There are a few people that I can reach out to when there is some kind of urgency, but I prefer to not bother them unless there is. However, let's see if anyone steps up by tomorrow and if not, I can request that one of these trustworthy individuals take a look if they have time.

Thank you for your patience.

[Starttoaster]

It's not urgent or anything. No need to disrupt people. I can just keep my go.mods pinned to my fork for eternity if need be, it's just not really my preference is all. I was mostly just interested to hear how this process is intended to go. I enjoy the idea of community PR reviews, but in practice, it's been my observation that it's not usually a great experience for would-be contributors awaiting reviewers because most devs put their focus on their day jobs and then log out at the end of the day to spend time with their families (understandably, because that's how they make money to live.)

Anyway, tl;dr -- no need to move mountains for me. Just wanted to set my expectations correctly so I wouldn't feel compelled to load this PR page every morning.

[raynigon]

LGTM

[gmlewis]

Thank you, @raynigon !
Merging.