Preview the new Team Discussions GraphQL API

We added new objects and mutations to our GraphQL API that allow you to read and manage team discussions. Team discussions is the first GraphQL feature to use a preview period. GraphQL previews work the same way as they do with our REST API. As always, if you want to find out about upcoming GraphQL schema changes, follow the GraphQL Changelog which now includes preview periods as well.

You can access the new objects and mutations during the preview period by providing a custom media type in the Accept header:

application/vnd.github.echo-preview+json

New GraphQL objects

New GraphQL fields

New GraphQL mutations

During the preview period, we may change aspects of the API based on developer feedback. If we do, we will not provide any advance notice of the changes, but we will announce them here on the developer blog.

We are really excited to see what integrations you develop around this API! If you have any questions or feedback, please let us know.

Label API improvements: emoji, descriptions, and search

We're happy to announce a new preview period for the Labels API. You can now use emoji in label names, add label descriptions, and search labels in a repository.

To access these features during the preview period, you must provide a custom media type in the Accept header:

application/vnd.github.symmetra-preview+json

During the preview period, we may change aspects of these API methods based on your feedback. If we do, we'll announce the changes here on the developer blog, but we won't provide advance notice.

If you have any questions or feedback, please contact us.

New endpoints

Updated endpoints

Preview required commit signatures for Protected Branches API

Protected Branches API now has a setting for requiring signed commits. We're adding three new endpoints for managing this setting. You can learn more about commit signing here.

New endpoints

How can I try it?

To access this functionality during the preview period, you’ll need to provide the following custom media type in the Accept header:

application/vnd.github.zzzax-preview+json

Take a look at the docs here. If you have any questions, please get in touch.

Preview the new Team Discussions REST API

Today, we released the REST API that allows you to read and manage team discussions programmatically, and we'll be announcing GraphQL support soon. You can access the REST API during the preview period by providing a custom media type in the Accept header:

application/vnd.github.echo-preview+json

During the preview period, we may change aspects of the API based on developer feedback. If we do, we will not provide any advance notice of the changes, but we will announce them here on the developer blog.

We are really excited to see what integrations you develop around this API! If you have any questions or feedback, please let us know.

New REST API endpoints

Updates to the Teams API documentation

We've also updated the location of our Teams REST API documentation. You'll now find the Teams API at the top level in the v3 documentation sidebar (no longer nested under Organizations). The team members, team discussions, and team discussion comments APIs are in the Teams section.

Weak cryptographic standards removal notice

Last year we announced the deprecation of several weak cryptographic standards. Then we provided a status update toward the end of last year outlining some changes we'd made to make the transition easier for clients. We quickly approached the February 1, 2018 cutoff date we mentioned in previous posts and, as a result, pushed back our schedule by one week. On February 8, 2018 we'll start disabling the following:

  • TLSv1/TLSv1.1: This applies to all HTTPS connections, including web, API, and git connections to https://github.com and https://api.github.com.
  • diffie-hellman-group1-sha1: This applies to all SSH connections to github.com
  • diffie-hellman-group14-sha1: This applies to all SSH connections to github.com

We'll disable the algorithms in two stages:

  • February 8, 2018 19:00 UTC (11:00 am PST): Disable deprecated algorithms for one hour
  • February 22, 2018 19:00 UTC (11:00 am PST): Permanently disable deprecated algorithms

For more details, head to the Engineering Blog.

Preview the new Organization Invitation API

We're releasing two new endpoints that allow you to programmatically invite new members to an organization using their email or user ID.

New endpoints

Changes to existing endpoints

To access these new API endpoints during the preview period, you must provide a custom media type in the Accept header:

application/vnd.github.dazzler-preview+json

During the preview period, we may change aspects of this API endpoint based on developer feedback. If we do, we will announce the changes here on the developer blog, but we will not provide any advance notice.

If you have any questions or feedback, please let us know!

Team Review Requests API becomes an official part of API v3

The Team Review Requests API just graduated from preview mode. It's now an official part of the GitHub REST API v3. As outlined in this blog post we will be making a breaking change to the API. Going forward, when you GET /repos/:owner/:repo/pulls/:number/requested_reviewers it will return both users and teams in a hash syntax, instead of only users. Please take the time to update your API's accordingly.

Preview media type no longer needed

If you used the Team Review Requests API during the preview period, you needed to provide a custom media type in the Accept header:

application/vnd.github.thor-preview+json

Now that the preview period has ended, you no longer need to pass this custom media type. Instead, we recommend that you specify v3 as the version in the Accept header:

application/vnd.github.v3+json

Please note, that GitHub Enterprise versions that do not yet support the Team Review Requests API will still require the custom media type.

Onward! Thanks again to everyone that tried out the Team Review Requests API during the preview period.

Issue Events API - Dismissed Review Event State

As previously announced, today we introduced a breaking change to the dismissed_review object in the Issue Events API and Issue Timeline API.

Going forward, the state will be a more informative string instead of an integer. Possible strings include commented, approved, or changes_requested. The API will no longer include the dismissal_commit_id field if a commit was not involved in the dismissal.

Please update your code accordingly, and let us know if you have any questions.

Preview adding a Lock Reason via the Lock Issue API

When locking an issue via the issues API, you can now provide an optional reason that will be visible to anyone who views the issue. Valid lock reasons are "off-topic", "too heated", "resolved", and "spam". Providing a lock reason can help make it clearer to contributors why an issue was locked, and what kinds of behavior may result in issues being locked in the future. This change will be available on both the REST API as well as the GraphQL API.

To set a lock_reason during the preview period, you must provide a custom media type in the Accept header: application/vnd.github.sailor-v-preview+json

During the preview period, we may change aspects of these API methods based on developer feedback. If we do, we will announce the changes here on the developer blog, but we will not provide any advance notice.

To our GitHub Enterprise customers: issue lock reasons will be available in the next Enterprise release (2.13), but not in the current version or older versions.

REST API changes

  • Issue and pull request responses now contain an active_lock_reason field that shows the lock_reason that was selected for an issue or pull request, if it is currently locked and a reason was provided.
  • You can use the REST API to pass an optional lock_reason parameter to the Lock issue at PUT /repos/:owner/:repo/issues/:number/lock.
  • Issue and pull request event responses now contain a lock_reason field that shows the lock_reason that was selected for a locked event.

GraphQL API changes

  • Lockable objects now contain an activeLockReason field that shows the lock_reason that was selected for an issue or pull request, if it is currently locked and a reason was provided.
  • You can now lock issues and pull requests through the GraphQL API through the lockLockable mutation, which includes an optional lockReason parameter.

If you have any questions or feedback, please let us know!

Issue Events API - Dismissed Review Event State

On January 17, 2018, we will introduce a breaking change to the dismissed_review event in the Issue Events API.

Currently, the REST API v3 passes an integer for state, but with this change it will pass a more informative string. Possible strings include commented, approved, or changes_requested. Along with this breaking change, the API will no longer include the dismissal_commit_id field if a commit was not involved in the dismissal.

Please update your code accordingly, and let us know if you have any questions or feedback!

Recent Posts

Subscribe to the RSS feed