Glenn Lewis

Thanks, @brondum. This is actually the perfect question for GitHub developer technical support: https://support.github.com/contact If they can show you how to accomplish what you want using the GitHub v3 API...

Thanks for your enthusiasm, @vikramzsingh , but this issue is not yet ready to work on. GitHub support needs to be contacted and we need to hear back from them...

@brondum - have you heard back from GitHub Tech Support on this issue? If so, please share your findings here. Otherwise, this issue will be closed in a couple weeks...

Hi @Osipion , and thank you for the report! This is totally my fault... I let #2062 go through code review without returning a populated struct. I apologize. This needs...

No rush, @Osipion - it is yours. Thank you!

Please hold off on these because we are walking a fine line between supporting current top-of-trunk GitHub versus many legacy versions of GitHub Enterprise.

After a quick scan of the changes from `v42.0.0` to `v45.2.0`, it is not obvious to me why there was a regression. To help quickly debug this, please add https://github.com/gmlewis/go-httpdebug...

Thank you! It looks like somehow `"allow_forking": false,` snuck in to the second one:  Now, the question is... how did this happen?!? Investigating...

Ah, yes! I believe I have seen this before. When you call `Repositories.Edit`, you need to only put the values into the request that you actually want to change. So...

Please see: * #2292 * #2309 You will need to change your code to not send the full repo info... but make a brand new `*github.Repository` struct with only the...