Preview of additional endpoints for GitHub Apps.

[gmlewis]

GitHub Developer Announcement:
https://developer.github.com/changes/2017-09-21-additional-endpoints-for-github-apps/

Woohoo! Lots of new endpoints to support.

I'm thinking that this is way too big for a single PR, and yet it would probably be silly to open up a separate issue for each endpoint... so how about if I add a checkbox task list to the endpoints in this issue and we can check them off as PRs address them? Obviously, the first PR will also need to add the new custom media type application/vnd.github.machine-man-preview+json in the Accept header and following PRs can just use it.

Here are the recently-added endpoints:

• GET /
• GET /emojis
• GET /events
• GET /networks/:owner/:repo/events
• GET /orgs/:org/events
• GET /users/:username/events
• GET /users/:username/events/public
• GET /users/:username/received_events
• GET /users/:username/received_events/public
• GET /repos/:owner/:name/community/profile
• GET /repos/:owner/:repo/community/code_of_conduct
• GET /repos/:owner/:repo/branches/:branch/protection
• GET /repos/:owner/:repo/branches/:branch/protection/restrictions
• GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews
• GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins
• PUT /repos/:owner/:repo/branches/:branch/protection
• DELETE /repos/:owner/:repo/branches/:branch/protection
• PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks
• DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks
• POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts
• PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts
• DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts
• DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions
• PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews
• DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews
• POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins
• DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins

Here are the endpoints for user-to-server requests:

• POST /repos/:owner/:repo/git/trees
• POST /repos/:owner/:repo/git/refs
• POST /repos/:owner/:repo/git/blobs
• POST /repos/:owner/:repo/git/commits
• POST /repos/:owner/:repo/git/tags
• PATCH /repos/:owner/:repo/git/refs/:ref
• DELETE /repos/:owner/:repo/git/refs/:ref
• PUT /repos/:owner/:repo/topics
• PUT /repos/:owner/:repo/contents/:path (create)
• PUT /repos/:owner/:repo/contents/:path (update)
• DELETE /repos/:owner/:repo/contents/:path
• POST /repos/:owner/:repo/statuses/:sha
• PUT /repos/:owner/:repo/branches/:branch/protection
• DELETE /repos/:owner/:repo/branches/:branch/protection
• PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks
• DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks
• POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts
• PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts
• DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts
• DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions
• PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users
• PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams
• PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews
• DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews
• POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins
• DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins
• PATCH /repos/:owner/:repo/issues/:number

It seems reasonable to assign multiple owners to this issue, and here in the comments we will attempt to clearly document who is working on which endpoints so that we don't waste anyone's time or effort.

Thank you in advance for contributing to this open source project!
Your assistance is greatly appreciated.

[elliott-beach]

I don't think those are new endpoints. I believe the above endpoints are now permissible for GitHub Apps to use, but we already support them for normal API clients. That includes user-to-server requests.

What is new is the machine-man preview header. We might as well add this header to every endpoint listed. I think I can do that in one pull request.

[gmlewis]

GitHub follow-on announcement:
https://developer.github.com/changes/2017-10-20-additional-endpoints-for-github-apps/

@elliott-beach - you investigated this previously... thank you! Do you want to take a look and see if this issue can be closed?

[dmitshur]

A status update here. We had a PR that implemented this issue (at least partially), but deferred merging it because of rationale posted in #736 (review).

Basically, if we wait long enough, this issue will get resolved on its own without us having to make any risky changes (back and forth) in go-github.

If someone really needs this functionality sooner, let us know here so we can make a better informed decision. So, the issue is in waiting/hold status until then.

[gmlewis]

Another GitHub Developer API follow-on announcement:
https://developer.github.com/changes/2018-10-11-new-endpoints-available-for-github-apps/

[gmlewis]

Closing issue as obsolete.