Syntax Highlighted Diffs

Unified and split diffs now feature syntax highlighting, which adds colors to your code to make its meaning and structure clearer. Now you can more easily understand the code that was changed in a commit, pull request, or review comment.

A diff with and without syntax highlighting

See it in action at dotnet/corefx or your favorite repository.

See results from all pull request status checks

Since we introduced the Status API, you've been able to improve the quality of your code by including the status of a pull request within the conversation timeline, for every push. Before today, you've only been able to see results from one service. Now you can see all your results at once, from multiple CI systems that test your code against different platforms to simultaneous security testing and code coverage analysis.

screenshot of status area with a few statuses

You can also see how the status of a pull request has changed over its history by clicking the icons listed next to individual commits.

screenshot of a commit with multiple statuses

If you're interested in how to set up your own statuses, take a look at our Status API docs along with this guide to building your own CI service. You can also check out some the services that use the Status API to help you keep your code clean, confirm your tests are passing, and make sure contributors have agreed to your CLA.

Introducing organization webhooks

Webhooks are now available at the organization level on Organization webhooks send events for all repositories in an organization. They also include new events for repository creation, team membership, and more.

org hooks

If you're extending GitHub into your internal systems, organization webhooks save you time by helping you configure integrations across multiple repositories in one place. The addition of organizational-level events, like team membership, open up new possibilties for integrators building applications that work with GitHub.

For all the details, check out our updated webhook developer guide.

Delete merged branches from your phone

After we introduced the merge button on mobile, we heard from many of you that you'd love to be able to delete merged branches on your phone too. Now you can!


Happy branching!

Linking merged pull requests from commits

We've been including the containing branches and tags on commit pages to give you more context around changes. Now, commits in a repository's default branch will also show you the pull request that introduced them.

no touching

In the pull request, you can see the discussion around why the commit was introduced, and get a clearer picture of the reason for the change.

As always, if you know the commit SHA, you can skip the commit page and search for the pull request directly.

For more information, check out our Help docs.

SVG Viewing & Diffing

In the spirit of making diffs of rich information easier to parse, SVG images are now viewable and diffable on GitHub!

SVG diff demo

As always, you can find more details in our help documentation.

Managing Issues and Pull Requests Across Repositories

Keep track of all of your issues and pull requests with the new Issues Dashboard and the new Pull Requests Dashboard.


When we rebuilt GitHub Issues earlier this summer, we made it easier to search and filter issues and pull requests in a repository. Now it's time to think bigger: these new dashboards let you manage your work across all of your repositories at once. You can find links to them at the top of your News Feed.

Use them to quickly find issues you've created. Or pull requests that mention your username. Or issues that have been assigned to you. Or go ahead and use any of our custom advanced search filters and create your own often-used search... the sky's the limit.

View Issue/Pull Request buttons for Gmail

If you're a Gmail user who gets GitHub notifications via email, you'll notice
that we've added subject-line links to issues and pull requests on notification

View Issue/Pull Request buttons

You can use these links to more quickly access content on GitHub -- all without
having to open your email notifications.

This feature is brought to you using Gmail's Actions in the Inbox.

Better Word Highlighting in Diffs

Commits, compare views, and pull requests now highlight individual changed words instead of the entire changed section, making it easier for you to see exactly what’s been added or removed.

Old and new highlighting behaviors

And, of course, it works great with split diffs, too:

New highlighting in split diff

Introducing split diffs

Split diff example

Diffs now come in two flavors, unified and split. Switch between them on pull request, commit, and compare pages using the toggle in the top right of the page. The mode you last used will become your preferred default.


Improved Audit Log

We've just released some major improvements to our organization audit logs. As an organization admin, you can now see a running list of events as they're generated across your organization, or you can search for specific activities performed by the members of your org. This data provides you with better security insights and gives you the ability to audit account, team, and repository access over time.

Audit Log

The audit log exposes a number of events like repository deletes, billing updates, new member invites, and team creation. You can see the activities of individual team members, along with a map that highlights the location where events originated. Using the new query interface, you can then filter all these events by the action performed, the team member responsible, the date, repository, and location.

Example Query

For more information on the audit log, check out the documentation.

Folder Jumping

You'll now start seeing expanded file listings on GitHub that look like this:

File listing with simplified paths

The grey text in the paths — in this case, java/com/netflix/ — means those three folders don't contain any other files. Click on the expanded path to save yourself extra clicks and jump directly to the first non-empty directory.

Expanded path

As a reminder, you can also type t to invoke the File Finder and jump directly to any file you like.

Clone Graphs

Our traffic graphs tab shows you a lot of information about who's visiting your repository on the web. We've added a new graph to this tab, showing git clone activity.

git clones traffic graph

You can use it to find out how many times your repository's source code is actually cloned in a given day, as well as how many unique GitHub users (or anonymous IP addresses) did the cloning.

For more information on traffic graphs, check out the documentation.

Inviting people to your organization

We've changed the process for adding new GitHub users to your organization. Starting today, users you add will be sent an email invitation. Once they accept this invitation, they'll become a member of your organization.

accepting an invitation

If you invite a user and they misplace their invitation email, they can always access the invitation from your organization's profile page.

invitation banner on organization profile page

Everyone on GitHub should be able to decide which organizations they'd like to join. This new process reinforces each person's privacy and security.

For more information on inviting people to an organization, check out our documentation. If you're using our API to add people to your organization, check out the new Team Memberships API.

GitHub Pages now runs Jekyll 2.2.0

We've upgraded GitHub Pages to support the latest version of Jekyll, the open source static site generator. Whether you're a new user or a savvy veteran, here are a few features that might help make publishing your next site a bit easier:

  • Native Sass & CoffeeScript support - Simply commit a .coffee, .sass or .scss file to your site's repository, and GitHub Pages will transparently output JavaScript or CSS when your site is published.
  • Kramdown as the default Markdown engine - In addition to better error handling, Kramdown supports MathJax, fenced code blocks, nested lists, tables, and much more.
  • Collections - With collections, Jekyll is no longer limited to just posts and pages—it can now publish all kinds of different documents, such as code methods, team members, or your favorite open source projects.
  • JSON data - .json files in the _data directory now get read in and are exposed to Liquid templates as the namespace (along with .yml files).

Under the hood there's also some great time savers such as front-matter defaults, the where and group_by filters, and a new starter site. Check out the full list of 300+ changes and new features added to Jekyll since version 1.5.1.

If you use Jekyll locally, simply run gem update github-pages, or follow these instructions to update your local build environment to the latest version.

Happy publishing!