Introducing new ways to build on your workflow

Whether you’re a team of 2 or 20,000, there's an app to simplify your work on GitHub Marketplace. Last week, we launched 2 new apps in the Marketplace that will make it easier to automate dependency updates and review code.

Code review

CodeFactor is a simple to use, automated Code Review service built by developers for developers. Setup with GitHub in seconds, to save time on code reviews and easily create issues directly from CodeFactor. Streamline your code review process and create actionable reports.

Dependency Management

Renovate brings automatic Javascript dependency updates to your workflow and supports npm, Yarn, Meteor, Docker or Bazel. It comes ready to go with a smart default configuration but provides a flexible configuration framework including scheduling and rules-based auto-merging to guide the updates you want to see in your repositories.

Ready to try out these new additions? See how they can help your team work better or discover even more tools in GitHub Marketplace.

GitHub Apps and Reactions for Team Discussions

Today we added new endpoints to the Reactions API preview that allow you to interact with reactions to team discussions and their comments. You can access these endpoints during the preview period by providing custom media types in the Accept header:

application/vnd.github.squirrel-girl-preview+json, application/vnd.github.echo-preview+json

Over the course of 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.

[Updated 04-20-18] OAuth access tokens now require the write:discussion scope when creating a reaction to a discussion, creating a reaction to a comment, or deleting a reaction.

New REST API endpoints

We've also enabled GitHub Apps for all endpoints related to team discussions. The endpoints listed below are available for both server-to-server and user-to-server requests.

Recently enabled REST API endpoints for GitHub Apps

We hope these changes help you build better integrations! If you have any questions or feedback, please let us know.

Require Multiple Approving Reviews for Protected Branches

The Protected Branches API now has a setting for requiring up to 6 approving pull request reviews. You can manage and view this setting from four 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.luke-cage-preview+json

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

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.

Recent Posts

Subscribe to the RSS feed