Private emails, now more private

GitHub has supported using an alternate "noreply" email address to author web-based commits for a while now. Starting today, there's another way to ensure you don't inadvertently publish your email address when pushing commits to GitHub via the command line.

Git uses your email address to associate your name to any commits you author. Once you push your commits to a public repository on GitHub, the authorship metadata is published as well.

If you'd like to ensure you don't accidentally publish your email address, simply check the "Keep my email address private" and "Block command line pushes that expose my email" options in your email settings.

email settings page with the block command line pushes that expose my email checkbox

You'll also want to configure Git to use your email. Don't worry—this won't affect your contribution graph. All commits will still be associated with your account.

Once you configure Git, commits will use your alternate "noreply" email address, and any pushes that don't will be rejected.

terminal showing the error message seen when a push is blocked by this setting

If you already have a private email address and would like to use this feature, check your email settings to make sure it's enabled. New private emails will have the option enabled by default.

For more information on keeping your email address private, check out the GitHub Help documentation.

Stay safe!

Disabling projects

Not every team manages their work on GitHub in the same way. Now you can disable repository and organization-wide Projects if you're not using them.

Disable GitHub Projects

Users with admin privileges on a repository can disable Projects by navigating to that repository's settings and unchecking the "Projects" box. Similarly, organization owners can disable Projects by navigating to an organization's settings and clicking "Projects" in the sidebar. On this page, unchecking the "Enable Projects for the organization" box will disable organization-wide Projects, and unchecking the "Enable Projects for all repositories" box will disable Projects for all repositories in the organization.

Disabling Projects hides the Projects tab from the repository and organization navigation, removes Projects from Issue and Pull Request sidebars, and hides Project-related events from Issue timelines. Disabled Projects are also inaccessible via API requests.

Projects can be re-enabled at any time, at which point all previously-disabled projects will be restored exactly as you left them.

Check out the help documentation and the Projects API page to learn more.

Open source license descriptions and metadata

Back in September we added open source licenses to repository overview pages. Now, when you view a repository's license, we'll tell you a bit more about it.

Screenshot of babel/babel license overview

If a project is licensed under a popular open source license like MIT, Apache, or GPL, you'll see a brief description of the license, along with an overview of what you can and can't do with the project.

Interested in incorporating the license metadata in your own project? The license descriptions and metadata are themselves open source, pulled from and made available via the license API.

We hope the additional license metadata helps you make informed choices, but please keep in mind that we’re not lawyers (at least most of us aren't). If you have any questions regarding the right license for your code or any other legal issues relating to it, of course, it’s always best to consult with a professional.

Happy open source licensing!

Restrict review dismissals with protected branches

There's a new way to reinforce your team's code reviews. Now you can specify who in your organization can dismiss reviews on a protected branch.

screenshot 2017-03-06 13 30 20

In the last year, we've been updating pull requests with features that help teams give feedback and make sure only the highest quality code makes it into their projects. You can leave, manage, request, and dismiss reviews, as well as protect branches and limit merging rights. With restricted review dismissals, you can also ensure important feedback gets addressed.

Completely remove the ability to dismiss reviews on a protected branch or restrict that ability to a subset of users or teams specified in your branch protection settings for any organization repository.

Introducing GitHub for Unity

Git helps millions of developers write and collaborate on code, but it's not always a practical choice for building games. With the GitHub for Unity extension, Unity game developers (artists and programmers alike) can better integrate Git and GitHub into their workflow, even if they're versioning large binary assets.

The GitHub for Unity extension integrates Git and GitHub directly into the Unity Editor. You can easily configure, collaborate, and manage your Git project in a dedicated window. The extension also includes Git LFS v2.0 support to store large binary assets and introduces file locking to help communicate with your team that you are working on difficult-to-merge files.


The GitHub for Unity extension is a first step towards unifying the GitHub and Unity workflows, and we'd love to hear your feedback to help guide us in the right direction. Watch for an alpha release over the next few weeks. We'll be making the project open source and publishing the extension in the Unity asset store soon after.

Many thanks to Emil "AngryAnt" Johansen for all his help in getting this project up and running.

Sign up now to get access to the GitHub for Unity plugin preview.

Powerful new features for businesses on

GitHub Business is now available

Today we're introducing a new Business offering that brings SAML single sign-on, automated provisioning and deprovisioning, 24/5 support, and guaranteed uptime to With direct access to our developer community and growing platform of integrators, teams can scale and work more efficiently using the tools they need. With the new offering, teams can work on or GitHub Enterprise for $21/user/month.

A closer look

GitHub Business plans

These new features build on how development teams already work on with unlimited private repositories, team and user level permissions, pull requests, code review, and project management tools. Now, they can also access:

  • Authentication through SAML single sign-on with support for Ping Identity, Okta, OneLogin, Azure AD, and Shibboleth
  • Automated access provisioning and deprovisioning
  • 99.95% uptime guarantee
  • 24 hours a day, five days a week support with a response time of less than eight hours

You might recognize some of these features from GitHub Enterprise, and you'd be right! By adding them, we hope teams will be able to manage people and tools with added security and efficiency, all while hosting code on We also expect they'll spend less time on overall administration and be able to grow without the need to manually add users or manage servers.

Teams that need to host GitHub on-premises or in a private cloud can do so with GitHub Enterprise, which has also received a few updates today for performance, reliability, and pull request efficiency. Read more about the latest release.

We'll be covering the specifics of this new offering in an upcoming webcast, along with an overview of how teams use GitHub.

Get started today

If you’re already using to host your projects, you can upgrade through your organization's Settings page. If you'd like to talk to someone first, get in touch with our Sales team—we'd be happy to help you out.

Announcing Open Source Guides

Participating in open source can be incredibly rewarding, but it's not always obvious how to make your first contribution, start a new project, or build an active community.

To make your journey easier, we're launching the Open Source Guides, a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to open source.

open source guides homepage

Open Source Guides are a series of short, approachable guides to help you participate more effectively in open source, whether it's:

  • Finding users for your project
  • Making your first contribution
  • Managing large open source communities
  • Improving the workflow of your project

These guides aim to reflect the voice of the community and their years of wisdom and practice. We've focused on the topics we've heard about most, and curated stories from open source contributors across the web.

Want to help improve the guides? The content is open source, so head over to github/open-source-guide to participate in community discussions about best practices.

See your project‘s history with the Activity View

Projects are a great way to keep your tasks organized on GitHub, and they‘re especially useful when working with a team. To make it easier to keep track of what‘s going on in a Project with lots of people, we‘re introducing the new Project Activity view, a way for you to view a history of all the activity that‘s happened in your project.

Screenshot of the Project Activity view

If you find that a particular card isn‘t where you left it, it could be because one of your teammates renamed it or moved it to a different column. The Project Activity view can help you track down these changes, so you can figure out exactly what‘s changed since the last time you looked at your Project.

Since we‘ve only recently started recording activity for this feature, your project‘s activity history won‘t go back much before January 27th, 2017. However, you‘ll be able to see any changes to your project after that date. It‘s time to start making history!

In the meantime, you‘re welcome to drop any questions, comments, or feedback about Project Activity into our help form.

Introducing Topics

Discover networks of similar repositories in a completely new way with Topics. Topics are labels that create subject-based connections between GitHub repositories and let you explore projects by type, technology, and more.


Click on a topic that interests you to find related repositories. Adding topics to your repositories will help other users discover your projects, too.


You may see suggested topics when adding a topic to a public repository. These suggestions are the result of machine learning and natural language processing applied to repository content. We're at the start of this new journey and rejecting suggestions that don't fit well will help us train our model for more meaningful results.

Our Help documentation will show you how Topics works today, and there's more to come. Topics will continue to grow as we learn more from you and better understand GitHub's role in project discovery. We can't wait to see how you use this new feature!

Filter pull request reviews and review requests

Pull request reviews are a great way to share the weight of building software, and with review requests you can get the exact feedback you need.

To make it easier to find the pull requests that need your attention, you can now filter by review status from your repository pull request index.

A screenshot showing the reviews filter menu in a repository pull request index

Use the Reviews filtering menu to see the pull requests still awaiting review, unreviewed pull requests on protected branches that require a review, approved pull requests that are ready to merge, and pull requests that have a review requesting changes.

You can also filter pull requests that have been reviewed by a specific user and quickly locate those that have required your review in the past to decide which needs your attention first.

A screenshot showing the global review requests dashboard

Finally, we've also added review requests to the global pull request dashboard so you can see all pull requests awaiting your feedback across all of your repositories and organizations.

You're welcome to drop any questions, comments, or feedback into our help form.

Manage pull requests with the GitHub Extension for Visual Studio

No need to toggle between windows, you can now manage pull requests without leaving Visual Studio. The GitHub Extension for Visual Studio includes a new pull request window that lets you review code, make changes, and push those changes back to GitHub. This release also provides support for upstream repository contributors to collaborate on a forked branch.

A Pull Request shown in the GitHub Extension

You can install the extension directly from the Visual Studio gallery or download it from

Last year we introduced the GitHub Extension for Visual Studio as an open source project under the MIT license. We welcome you to log issues and contribute in the extension repository.

Navigate file history faster with improved blame view

Whether you're debugging a regression or trying to understand how some code came to have its current shape, you'll often want to see what a file looked like before a particular change. With improved blame view, you can easily see how any portion of your file has evolved over time without viewing the file's full history.


Check out the GitHub Help documentation for more information on using git blame to trace the changes in a file.

Visualize your project's community

A new graph is available in the Graphs tab to visualize your repository's data. With the dependents graph, you can now explore how repositories that contain Ruby gems relate to other repositories on GitHub.

If you're an open source maintainer, this means you can find out more about the community connected to your project in addition to projects that depend on your repository and its forks.

Screenshot of dependents page

The page starts with a list of the latest repositories to depend on your repository, making it easier to discover the newest members of your community. It also allows you to filter by either packages, which are other repositories that are gems, or applications, which are other public repositories that aren't gems themselves but use your gem.

The dependency graph works for Ruby gems today, and we plan to expand support to other package ecosystems in the future. For more on what graphs can tell you about your project, check out our Help guide on Graphs.

Search commit messages

You can now search for commits from either the main search page or within a repository. Quickly discover who removed set -e or find commits that involved refactoring.

Commit search

Check out the GitHub Help documentation for more information on how to search commits.

Resolve simple merge conflicts on GitHub

You can now resolve simple merge conflicts on GitHub right from your pull requests, saving you a trip to the command line and helping your team merge pull requests faster.

Demonstrating how to resolve a merge conflict

The new feature helps you resolve conflicts caused by competing line changes, like when people make different changes to the same line of the same file on different branches in your Git repository. You'll still have to resolve other, more complicated conflicts locally on the command line.

For more on merge conflicts and how to make them disappear on GitHub and on the command line, check out the GitHub Help documentation.