Inform and Act

Read our official statements regarding recent executive orders and find resources to help you take action. Learn more

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.

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!

The New GitHub Issues

We've rebuilt GitHub Issues to be smarter: search smarter, filter smarter, and manage your issues and pull requests smarter.

The New GitHub Issues

If you want to see it in action, check out Bootstrap's issues. To learn more, read on.

Search and filter

A big part of managing your issues and pull requests is focusing on what needs to happen next. The new search box at the top of the page gets you there faster:


You can filter your search results by author, label, milestone, and open/close state. You can also use any of our advanced search terms to find just what you're after.

Watch an issue evolve

Over time, titles change, labels and milestones get closer to completion, and issues get new owners. Now you have better insight into these changes.

Issue Events

Pull requests also make use of our new Deployments API, which lets you know exactly when a pull request has made it to your testing, staging, and production environments:


The new labels & milestones pages

Labels and milestones can help with managing a project's issues, but it's also important to make sure you can manage the labels and milestones themselves. Two new pages offer a better vantage point into the overall health of your project:

The new labels page (example):


...and an updated milestones page (example):


All the small things

There's a slew of smaller changes that went into this release of Issues as well:

  • You'll get a notification if an issue is assigned to you.
  • No more mixing: the "issues" tab will only show you issues, and the pull requests tab will still only show pull requests. Want to see them together again? Just remove the is:issue or is:pr filter from your search query.
  • If you use Task Lists, we'll show the overall progress on that issue or pull request on the listing page:
    Task List progress
  • You can add labels and assign pull requests to milestones even if you have issues disabled on your repository.
  • New keyboard shortcuts mean it's quick to filter down to what you want. Type ? on an issues listing to get a list of the available keyboard shortcuts.
  • You can now triage multiple pull requests at once by selecting them and changing their label, assignment, state, or milestone, just like issues.

Learn more about Issues

Check out our updated guide on Mastering Issues to learn more about workflows and how to make issues work for you. And, of course, we've updated our help documentation for the new GitHub Issues, so if you run into any problems, be sure to give them a peek.

A better Issues

Software is about getting things done: either by doing the work, or planning out how to do the work. We hope the new GitHub Issues gets you there quicker and happier.

Introducing a simpler, faster GitHub for Mac

Following the recent release of GitHub for Windows 2.0, we’ve been working hard to bring our two desktop apps closer together.

We’ve just shipped a significant new update to GitHub for Mac, with simplified navigation and a renewed focus on your cloned repositories.

With this update, you’ll be able to spend less time navigating lists of respositories, and more time focusing on your repositories and your branches.

Repositories Next

Simplified Navigation

The sidebar now features all your repositories grouped by their origin, and the new toolbar lets you create, clone, and publish additional repositories quickly. You can also press ⇧⌘O to filter local repositories from those associated with GitHub or GitHub Enterprise, and switch between them.

Cloning repositories from GitHub

Fewer steps are required to clone repositories from GitHub Enterprise or You can now press ⌃⌘O, type the repository name, and then press Enter to clone the repositories you want and need.

Cloning GitHub Repositories

Switching and creating new branches

The branch popover (⌘B) has moved to the new toolbar, and now has a “Recent Branches” section that provides a convenient way to switch between all of your in-progress branches.

Branch creation (⇧⌘N) has moved to its own popover, and you can now create a new branch from any existing branch.

Switching and creating new branches

How do I get it?

GitHub for Mac will automatically update itself to the latest version. To update right away, open the “GitHub” menu, then “Check For Updates…”, or visit to download the latest release.

NOTE: This release and future releases of GitHub for Mac require OS X 10.8 or later. If you are still running OS X 10.7, you will not be updated to this release.


We’d love to hear what you think about this release. If you have any comments, questions or straight-up bug reports, please get in touch.

Pay for GitHub with PayPal

GitHub is now accepting PayPal, in addition to credit cards, to pay for personal plans and organization accounts.


We've been working closely with Braintree to deliver PayPal payments using their brand new APIs and we're pretty excited with the result. You can use PayPal whether you're just signing up, looking to upgrade, or want to switch off credit card payments.

Paying for GitHub with PayPal has never been easier or looked better, and we're hoping that no matter where you are in the world, you'll be able to use GitHub to build something great!

For more information, see "Paying for your GitHub user account" or "Paying for your GitHub organization account" in the GitHub Help.

GitHub Enterprise 11.10.341 Release

GitHub Enterprise releases are all about offering large companies more of GitHub to deploy in their own environments, and today's release is no exception. We've added a number of features that improve speed, flexibility, security, administration, and more.

Faster Git operations

Smarter caching on the server side now optimizes the initial counting objects phase of all Git network operations. This drastically reduces the CPU time required by Git network operations, allowing more simultaneous clones and fetches without increasing the load on the Virtual Machine. You'll also find Git clone, fetch, and pull to be an order of magnitude faster, especially for large repositories.


Activity data across all your projects

See what's happening across all projects on GitHub Enterprise in one place, from users and organizations to issues, pull requests, and code review comments. The Activity Dashboard compiles all this data and presents it in easy-to-read graphs, along with past data from the same time period.


LDAP configuration improvements

You can now better configure GitHub Enterprise to your company's LDAP setup. Nested user groups are supported, users can change their username and still be mapped to the same distinguished name, and you can specify the name of attributes to map to imported fields.


Advanced settings for blocking force pushes

More options for blocking force pushes enable you to configure settings as you need. You can now block force pushing for a specific user, on the default branch of an organization's repositories, and for all branches on a single repository.


... and so much more!

If you're currently using GitHub Enterprise, you can download this release from the Enterprise website. If you want to give GitHub Enterprise a try, request a 45-day free trial.

Update: After this morning's announcement, we noticed an issue with the original 11.10.340 release and have issued a patch release with a fix. All links in the blog post above now redirect to the correct release notes and download page. We're sorry for any confusion this may have caused. If you have any issues with the newest release, please contact us at

Introducing the Revert Button

We've all merged bad pull requests and wanted to roll back the changes without having to rely on Git commands. Starting today, you can easily revert a pull request on GitHub by clicking Revert:

You'll be prompted to create a new pull request with the reverted changes:

More details about reverting pull requests are available in Help.

A better branches page

Branches are an essential part of collaborating using GitHub Flow. They’ve always been cheap and easy to create within a GitHub repository, and today we’re making branch management more straightforward.

At the top of any repository page, click Branches to see an overview of the branches across your project.

Atom’s branches page

You can quickly filter the branches you’ve created, and see which branches are most active. New sections on the page also make it more obvious how you need to take action on the branches in your repository—whether that’s cleaning up stale branches, examining a branch with a failing test, or sending a pull request for the branch you just pushed.

See the branches you care about

Need more help? See Creating and deleting branches within your repository and Viewing branches in your repository in GitHub Help.

Octicons for everyone!


Two years ago we started using Octicons—our icon font—on GitHub. We use them in many of our sites and include them in Atom. Now we are making them available for download to everyone else. Go forth, and octiconify the world.

Say hello to GitHub for Windows 2.0

Two years ago we launched GitHub for Windows as the easiest way to use Git and GitHub on Windows. Today we're shipping a major update that helps you focus more on your work and gives you a more streamlined way of getting that work to and from GitHub.

Your work, emphasized

When you write code, your workspace should be as distraction free as possible. We've focused GitHub for Windows so that what you're working on is front and center.

GitHub for Windows 2.0

Everything you need in one screen

The less time you spend navigating through menus and options, the more you can focus on getting things done. Now your local repositories are always available in the left sidebar, and you can create, clone, and publish repositories without having to navigate to a new screen.

Creating and publishing repositories

The sidebar also groups your repositories by where they originated, so repositories associated with GitHub Enterprise are easy to distinguish from your personal projects and it's simple to switch between them.

More of GitHub locally

GitHub for Windows also now supports more of the GitHub feature set. You can pick an ignore file template for your project when you create a repository, and you can include emoji and gifs in your commit messages.

What are you waiting for?

If you have GitHub for Windows installed it will automatically update to the latest version. If you don't have it installed, download GitHub for Windows 2.0 at

PSD Viewing & Diffing

We've supported image viewing and diffing for quite some
time now, but today we're happy to announce that we're adding PSD files to the
images we support for this. Any PSD assets in your repositories will be treated
just like images, meaning you can view them inline and use our three image view modes
to see what's changed in a commit.

Onion skin

As always, read more about it in our help documentation.

Nested task lists

The most organized people know that finishing a task rarely involves just one step. That's why we're excited to announce nested task lists!

For example:

- [ ] Figure out wormholes
  - [ ] Call @arfon
  - [ ] Research ([docs](
  - [ ] Build prototype #15
  - [ ] Test run #43 @world-domination/time-travel
- [ ] ...?
- [ ] Profit!

Now renders as:

nested task lists

Updates work as before: check items on and off to update their completion state.

For more information, see the Writing on GitHub article in the GitHub Help.

GitHub Pages <3

We're excited to share some recent improvements to GitHub Pages, which you may have already noticed rolling out over the past several weeks:

Additional metadata for organization pages

Many large organizations like Adobe, Netflix, and The Consumer Financial Protection Bureau use GitHub Pages to showcase their open source efforts. We've just made it easier to create beautiful pages for you and your projects by exposing additional project and organization metadata to the site.github namespace:

  • contributors - A list of your project's contributors, as returned through the contributors API
  • public_repositories - A list of your public repositories as returned from the repositories list API
  • organization_members - A list of your organization's public members as returned from the organization members API

Each of these new elements expose complete user/repository objects to Jekyll, and can eliminate the need for making client-side API calls when showcasing your open source efforts on GitHub. For more information on displaying metadata within your Jekyll site, see Repository metadata on GitHub Pages.


We recently open-sourced and white-listed the jekyll-sitemap plugin. By simply adding the plugin to your site's config file, Jekyll will automatically generate a sitemap, making it easier for search engines to index your site's content. For more information, see Sitemaps for GitHub Pages.

Better build feedback

You may have already noticed that following some successful builds you may receive a warning email with helpful feedback about CNAME errors, upgrading your Markdown interpreter, or ensuring your custom domain is properly configured.

Additionally, if your page build does fail, we'll provide you with a link to an error-specific help article so that you can get the problem sorted out in no time.

PageBuild events

A few weeks ago we introduced the PageBuild webhook. If you subscribe to the page_build event, we'll ping your application with the result of your site's build following each push. You can use this information to better integrate GitHub Pages with your current development workflow.

Happy documenting!