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.

OctoTales • GREE

Open source software development practices are growing all over Japan, and one company at the forefront of these efforts is GREE. Their mobile social gaming platform connects 230 million users worldwide, and they've been building it using GitHub Enterprise since 2012. We recently had the pleasure of talking with GREE for our latest episode of OctoTales.

オープンソース・ソフトウェアの手法を用いた開発ワークフローは日本中に浸透して行っていますがこの開発スタイルを取り入れている企業の中にGREE社があります。GREEのソーシャルゲームプラットフォームは世界中で2億3千万人以上のユーザーが利用していまして、2012年からGitHub Enterprise を活用しています。OctoTalesの最新エピソードではGREEのメンバーとお話をしました。

Are you using GitHub in Japan and looking for some resources? We've translated our Git Cheat Sheet into Japanese, and our GitHub & Git Foundations videos now have Japanese subtitles.

GitHubの日本語のリソースも増えています。Git Cheat Sheet を日本語に訳しましたし、 GitHub と Gitの基礎のビデオシリーズ にも日本語の字幕を追加しました。

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.

Gist Design Update

Today, we're shipping a design update to Gist to give it that same look and feel you're used to on

Updates include:

  • Redesigned conversations
  • Redesigned revisions view
  • Redesigned user profile
  • Redesigned navigation to match
  • Additional clone/embed options
  • And many more!


We hope you enjoy all the great new updates to Gist.

Happy Gisting!

Locking Conversations

Starting today, you can lock the conversation on an issue or a pull request. If you're a collaborator on a repository, click the lock in the sidebar of an issue page to lock the thread:

Lock link

This will be reflected in the conversation timeline:

Issue event

Users who aren't collaborators on the repository won't be able to comment further:

Locked form

Repository collaborators will still be able to continue the conversation on a locked thread if they'd like.

Remember that, in addition to conversation locking, you can also block or report users to help keep GitHub a safe community for everyone.

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

Patchwork Night UK Edition

We're happy to announce a new Patchwork hack night at the beautiful ustwo studio in London.


Learning open source, together

Patchwork is a hands-on workshop for learning Git and GitHub. We'd love for you to join us. There will be snacks for fortified hackin', lots to learn, and new friends to be made.

Forks you don't eat with? Branches not made of wood?

Attendees will leave with a merged pull request, a square on your contributions graph, and confidence to get more involved in the exciting world of open source.

Let's do this

Are you ready to show the open source community what you've got? Myself, @muan, @andrew, @lildude, @shiftkey, @tobiasahlin, other GitHub staff and community mentors will be on hand to answer your questions.

No coding experience required!

  • Want to learn Git and Github? RSVP as an attendee.
  • Want to help guide future open source maintainers and contributors? RSVP as a mentor.


  • For: Git and GitHub beginners.
  • When? Wednesday, June 18th from 6:30-8:30pm.
  • Where? ustwo's studio at 62 Shoreditch High St, London E1 6JJ, United Kingdom.
  • Bring: Make sure you bring your laptop with Git-it installed (we'll help you if you get stuck).

Once registered, you'll receive an email a few days before the event with a few more details on Git-it, so you can hit the ground running.

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.

Diversity and Feedback at GitHub

Back in April I said we would share the new initiatives we're launching to ensure GitHub is a welcoming and inclusive company. This work is long term and will remain a constant focus for us, but I wanted to share some of the progress we've made so far.

A few weeks ago we identified a number of areas we'd like to improve, and so far we've focused our early efforts on three in particular: the experiences of women at GitHub, improving feedback, and supporting diversity both internally and externally.

Task Force

In April, a group of employees formed a task force to explore the experiences of female employees at GitHub and surface any issues that might not be obvious. The group has been gathering feedback from some of the women at the company, meeting regularly to discuss, and sharing this feedback internally.

The task force has been using a repository to discuss new ideas and individual experiences, which has been helpful in opening up the discussion to the whole company. We know not everyone wants to share their experiences openly and we are working on developing a formal feedback system (more on that later), but we have already received some good ideas and feedback from the people who have participated.

The big themes we've heard so far:

  • We all need to get better at respectful and constructive feedback and communication, both verbal and written.
  • We need to better educate employees on everyone's role and function, and we need to especially get better about understanding and appreciating people in non-developer roles.
  • We need to do more to celebrate and increase diversity within the company, including women.

Some of the things we're doing based on this feedback:

  • We’re in the planning stages of designing a diversity and communication training curriculum for GitHub employees with input from Hubbers and external experts. Topics will include diversity training, effective communication, giving and receiving peer feedback, and conflict resolution.
  • We have started informal internal workshops focused on developing leadership skills, and we are looking to create more formalized training programs by early next year.
  • We have started an internal cross-training program where different teams within GitHub educate other teams on what they do. This is part of our push to help everyone understand how different roles and skills contribute to making GitHub work.

The task force will continue to meet, gather feedback, and discuss ways we can improve, and we're encouraging everyone to participate in these discussions. We will also continue to gather feedback from every employee so we know what we can do better.

Improving Feedback

GitHub has historically operated without any formal feedback system. While we've tried to encourage employees to give each other direct feedback, the lack of clear process and training left Hubbers on their own to understand how and when to have conversations with other people in the company.

We are currently in the process of developing and implementing a formal, documented feedback system for everyone in the company. So far we've begun rolling this out in Engineering, our largest department, and we intend to take it further. Our goal is to ensure that everyone has frequent, constructive feedback and someone they can go to with questions or concerns who can help them. We want people to know where they stand and that someone has their back, and in the past we haven't been good at this.

We've also been expanding our HR team since hiring a head of HR in January and are using their experience to help develop this system, from the communication training program I mentioned earlier to clear steps to take when you need help.

Supporting Diversity

Supporting diversity has always been important to us but recently we've been ramping up our support, participation, and sponsorships for community groups and events that promote diversity in tech. This includes sponsoring more groups focused on helping women in tech and sending employees to conferences focused on these issues, such as the The Grace Hopper Celebration of Women in Computing.

We’re also planning to use the community space at our San Francisco headquarters to sponsor and host more frequent diversity-focused events, including events led by community organizations, official GitHub events, classes, and meetups.

If you’re interested in using our space, are seeking sponsorship, or have an idea for how we can help, please let us know:

One of the biggest lessons I've learned over the past few weeks is improving isn’t just about developing solutions - a huge part is getting good at surfacing problems. Without a solid feedback system, without talking to people regularly, without explicitly focusing on these issues, without asking people how they're doing and having them feel safe telling you the truth, you'll never know what the real problems are. If people feel like they can't speak up, you'll never hear what they have to say, and you'll never know they're not saying it.

Making GitHub a great place for everyone is something we have to work towards every day. In the future we’ll continue to post about new initiatives, updates on our progress, information on how our philosophies around things like sponsorships are evolving, and details on events we're hosting or participating in. Consider this post the first of many.

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.

Improving GitHub for science

GitHub is being used today to build scientific software that's helping find Earth-like planets in other solar systems, analyze DNA, and build open source rockets.

Seeing these projects and all this momentum within academia has pushed us to think about how we can make GitHub a better tool for research. As scientific experiments become more complex and their datasets grow, researchers are spending more of their time writing tools and software to analyze the data they collect. Right now though, these efforts often happen in isolation.

Citable code for academic software

Sharing your work is good, but collaborating while also getting required academic credit is even better. Over the past couple of months we've been working with the Mozilla Science Lab and data archivers, Figshare and Zenodo, to make it possible to get a Digital Object Identifier (DOI) for any GitHub repository archive.

DOIs form the backbone of the academic reference and metrics system. With a DOI for your GitHub repository archive, your code becomes citable. Our newest Guide explains how to create a DOI for your repository.


Academic accounts on GitHub

We also know that as a scientific researcher, sometimes you're going to want to work privately. That's why we've created a discount where individual academic researchers can receive a free micro plan with 5 private repos, while research groups can receive a free silver plan with 20 repos.

To set up an academic account on GitHub, first associate an academic email address with your account and then request a GitHub Education discount.

Awesome science happening on GitHub

If you're interested in seeing all the science happening on GitHub, check out some of our favorite projects, including rOpenSci. This group recently held a Hackathon at GitHub HQ, where their team worked with collaborators from academia, business, and various research labs to build open source tools for science.

GitHub Town Hall: Open Source and the Enterprise

GitHub Town Hall: Open Source and the Enterprise

Lots of businesses today are experimenting with open source, both by maintaining open source projects and also by internalizing open source workflows. However, adopting open source tools in a business context often presents a steep learning curve. Implementation isn't always straightforward, and cultural changes can sometimes be long-term and tedious.

On Wednesday, May 28, 2014, we've invited a set of speakers to GitHub HQ to talk more about this topic for our first ever public Town Hall, moderated by Eric Knorr, Editor In Chief of InfoWorld. Join us to hear more about how open source is evolving inside companies from:

  • Chris Aniszczyk, Twitter
  • Kurt Chase, Autodesk
  • Dominik Tornow, SAP
  • Nate McWherter, GE

Event Details

Update: If you're not able to attend the Town Hall in person, we will have a live stream available. We'll share the link here and on Twitter next week before the event starts.

Change the visibility of your Gists

Because we love sharing, we use Gist every day to pass snippets of code, writing, notes, and more to each other. One thing we've noticed with all this sharing is that we've all created Public Gists that we meant to make Secret and vice versa.

Starting today, you can change the visibility of your Gists whenever you want. When editing a Gist you'll now notice a new option to toggle the visibility between Public and Secret. The URL for your Gist will never change, just its visibility.


For more information on the differences between Secret and Public Gists, please see this helpful document.

Happy Gisting!

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!