Add support for enable/disable private vulnerability reporting on repositories

[vandanrohatgi]

Closes #2883

• go generate
• go vet
• go test

Please let me know if the method names are not descriptive enough or just need to be changed.

Also, something that's been bugging me. In my previous PR, I did some actual testing aside from the unit tests. While not present in CONTRIBUTING.md , is it advisable/necessary/optional to perform actual testing (importing the library, calling the new method and examine response).

[codecov]

Codecov Report

Merging #2887 (4338ba0) into master (a0e8f35) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #2887   +/-   ##
=======================================
  Coverage   98.06%   98.06%           
=======================================
  Files         140      140           
  Lines       12269    12293   +24     
=======================================
+ Hits        12031    12055   +24     
  Misses        162      162           
  Partials       76       76           

Files Changed	Coverage Δ
github/repos.go	98.89% <100.00%> (+0.03%)	⬆️

[gmlewis]

Thank you, @vandanrohatgi !
A few minor tweaks, please, then we will be ready for a second LGTM+Approval from any other contributor to this repo before merging.

[gmlewis]

Also, something that's been bugging me. In my previous PR, I did some actual testing aside from the unit tests. While not present in CONTRIBUTING.md , is it advisable/necessary/optional to perform actual testing (importing the library, calling the new method and examine response).

In this repo, we do not typically add to the integration tests anymore.
They were extremely helpful in the early design of the repo, but in my opinion, the surface area of this API is so huge that it would be an onerous task to attempt to keep up-to-date in addition to the unit tests.

Having said that, we place a high value on unit tests in this repo and want every endpoint to be exercised "round-trip" with an in-memory http server to verify that every one looks like it should work in real practice.

So you are proceeding along just as planned, and we really appreciate your contributions, @vandanrohatgi !

Keep up the great work! 😁 ❤️

[vandanrohatgi]

Thank you for making this project such a pleasure to work with!

[gmlewis]

Thank you, @vandanrohatgi !
LGTM.

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

[mnafees]

LGTM 👍🏽

[gmlewis]

Thank you, @mnafees !
Merging.