CodeConf 2015: Early Bird Tickets and Call for Proposals

codeconf header 1

CodeConf 2015, GitHub's premiere open source event, will take place on June 25-26 in Tennessee. We hope you'll join us for what is sure to be a special community experience at the Bell Tower, in the heart of downtown Nashville.

We're pleased to announce that CodeConf is accepting proposals for talks beginning today. For guidelines around submissions, please take a look at the detailed form. The call for proposals ends May 10th at 11:59pm PDT.

CodeConf is dedicated to amplifying new voices from the amazing open source community. We will feature thoughtful and compelling sessions that will leave all attendees thinking differently about the open source ecosystem. We will also be celebrating the unique American city of Nashville by featuring local cuisine and artists throughout the conference. CodeConf will culminate in a party at the historic Country Music Hall of Fame, only a few blocks away from the Bell Tower.

Get your early bird ticket now!. On May 25, ticket sales will increase by $100. Follow @codeconf on Twitter for regular updates on content, training sessions, and more.

Come with an open mind, and leave a better contributor.

Game Off III - Everyone's a Winner

Last month, we challenged you to fork a game repository and do something awesome with it based on our Tron-inspired theme, "the game has changed". Below are the submissions. They're all super fun and playable in your browser, so click around and enjoy.

And remember - while the contest has officially ended, the fun doesn't stop here. All of these games are open source. Read the code, fork the repository, and help improve them even further. Make them harder, make them easier, add more octocats, or put your own spin on them.

Now for some real user power...

Business Frog Jumps to Conclusions

Business Frog Jumps to Conclusions

Join Business Frog as he jumps through the dystopian world of software project management » view the source · play

Umbilicus Ascension

Umbilicus Ascension

A 4-player cooperative platformer where only 1 player can win » view the source · play

A Lighted Story

A Lighted Story

An HTML5 action game and interactive fiction » view the source · play



A 2D infinite musical platformer set in the dark » view the source · play

Floodgate Dungeon

Floodgate Dungeon

An infinite runner game set in a dungeon » view the source · play

Upstream Commit

Upstream Commit

Dodging branches may seem easy at first, but how long can you hold up as you approach terminal velocity? » view the source · play



A Tetris-like game where you have to collect code blocks and deploy them into applications » view the source · play



Avabranch has never been so much fun » view the source · play

Typing Knight

Typing Knight

A veggie-based clone of Fruit Ninja for your browser, where you type to slice » view the source · play



A 2D sci-fi platformer » view the source · play



Descend as many levels into the maze as possible without meeting your demise » view the source · play

Dig Deep

Dig Deep

Dig as deep as you can and collect as much gold as you can without getting killed » view the source · play

Board Free

Board Free

The classic SkiFree, but with snowboards » view the source · play

Pappu Pakia Fighter Cat

Pappu Pakia Fighter Cat

Nyan out of 10 cats prefer it » view the source · play



An Octocat and a jetpack. What's not to like? » view the source · play



Snake meets Tron » view the source · play

Flippy Cat

Flippy Cat

A clone of a clone of a Flappy Bird game, but with a twist » view the source · play

GitHub's 2014 Transparency Report

Like most online services, GitHub occasionally receives legal requests relating to user accounts and content, such as subpoenas or takedown notices. You may wonder how often we receive such requests or how we respond to them, and how they could potentially impact your projects. Transparency and trust are essential to GitHub and the open-source community, and we want to do more than just tell you how we respond to legal notices. In that spirit, here is our first transparency report on the user-related legal requests we received in 2014.

Types of Requests

We receive two categories of legal requests:

  1. Disclosure Requests — requests to disclose user information, which include:
  2. Takedown Requests — requests to remove or block user content, which include:

Disclosure Requests

Subpoenas, Court Orders, and Search Warrants

We occasionally receive legal papers, such as subpoenas, that require us to disclose non-public information about account holders or projects. Typically these requests come from law enforcement agencies, but they may also come from civil litigants or government agencies. You can see our Guidelines for Legal Requests of User Data to learn more about how we respond to these requests.

Since many of these requests involve ongoing criminal investigations, there are heightened privacy concerns around disclosing the requests themselves. Further, they may often be accompanied by a court order that actually forbids us from giving notice to the targeted account holder.

In light of these concerns, we do not publish subpoenas or other legal requests to disclose private information. Nonetheless, in the interest of transparency, we'd like to provide as much information about these requests as we can.

Subpoenas, Court Orders, and Search Warrants Received

In the data below, we have counted every official request we have received seeking disclosure of user data, regardless of whether we disclosed the information or not.

There are several reasons why information may not be disclosed in response to a legal request. It may be that we do not have the requested data. It may be that the request was too vague such that we could not identify the data, or that it was otherwise defective. Sometimes the requesting party may simply withdraw the request. Other times, the requesting party may revise and submit another one. In cases where one request was replaced with a second, revised request, we would count that as two separate requests received. However, if we responded only to the revision, we would count that only as having responded to one request.

  Information Request Totals.
  Total Requests: 10.
  Percentage of Requests Where Information Was Disclosed: 70%.
  Percentage of Disclosures Where Affected Users Were Provided Notice: 43%.

It is also our policy to provide notice to affected account holders whenever possible; however, as noted previously, we are often forbidden by law from providing notice to the account holder. The following chart shows the breakdown of how frequently we are actually allowed to provide notice to the affected account holders.

  Percentage of Requests Resulting in Disclosure and Notice.
  Nothing Disclosed: 30%.
  Some or All Requested Information Disclosed: 70%.
  Looking only at the cases where information was disclosed:
  Provided Notice Before Disclosure: 43%.
  Prohibited from Providing Notice: 57%.
Accounts Affected by Subpoenas, Court Orders, and Search Warrants

Some requests may seek information about more than one account. Of the ten information disclosure requests we received in 2014, only forty total accounts were affected. For comparison, forty accounts is only 0.0005% of the 8 million active accounts on GitHub as of December 2014.

Types of Subpoenas, Court Orders, and Search Warrants Received

In 2014, we only received a handful of subpoenas. We did not receive any court orders or search warrants requiring us to disclose user data:

  Types of Information Requests.
  Subpoeanas: 10.
  Court Orders: 0.
  Warrants: 0.

To help understand the difference between the numbers above:

  • Subpoenas include any legal process authorized by law but which does not require any prior judicial review, including grand jury subpoenas and attorney-issued subpoenas;
  • Court Orders include any order issued by a judge that are not search warrants, including court orders issued under the Electronic Communications Privacy Act or Mutual Legal Assistance Treaty orders; and
  • Search Warrants are orders issued by a judge, upon a showing of probable cause under the Fourth Amendment to the U.S. Constitution, and particularly describing the place to be searched and the data to be seized

As noted above, many of the requests we receive are related to criminal investigations. We may also receive subpoenas from individuals involved in civil litigation or government agencies, such as the Federal Trade Commission, conducting a civil investigation. The following pie charts show the breakdown of the different types of requests we received in 2014.

  Types of investigations leading to information requests.
  Criminal: 60%.
Civil: 40%.

  Types of subpoenas received in 2014.
  Grand Jury Subpoenas: 50%.
  FTC Subpoena: 20%.
  DMCA Subpoena: 10%.
  California State Court Subpoena: 10%.
  FBI Subpoena: 10%.

National Security Orders

There is another category of legal disclosure requests that we are not allowed to say much about. These include national security letters from law enforcement and orders from the Foreign Intelligence Surveillance Court. If one of these requests comes with a gag order—and they usually do—that not only prevents us from talking about the specifics of the request, but even the existence of the request itself. The courts are currently reviewing the constitutionality of these prior restraints on free speech, and GitHub supports the efforts to increase transparency in this area. Until such time, we are not even allowed to say if we've received zero of these reports—we can only report information about these types of requests in broad ranges:

  Total National Security Orders Received: 0 to 249.
  Total Number of Accounts Affected: 0 to 249.

Takedown Requests

Government Takedown Requests

In 2014, we started receiving a new kind of takedown request—requests from foreign governments to remove content. We evaluate such requests on a case-by-case basis; however, where content is deemed illegal under local laws, we may comply with such a request by blocking the content in that specific region.

Whenever we agree to comply with these requests, we are committed to providing transparency in at least two ways: by giving notice to the affected account holders, and also by posting the notices publicly. This is the approach we took, for example, when we were contacted last year by Roskomnadzor, the Russian Federal Service for Supervision of Communications, Information Technology and Mass Media. We reached out to each of the account holders to let them know we had received the request and, when we eventually blocked access to the content in Russia, we posted the notices to a public repository. Since that repository is public, anyone can view the notices to see what content was blocked. Here are the high-level numbers of content blocked in Russia:

  Roskomnadzor Notices Totals.
  Total Notices Processed: 3.
  Total Accounts Affected: 9.

To date, other than the Roskomnadzor notices, we have not blocked content at the request of any other foreign government. And because we are committed to transparency, if we agree to block content under similar circumstances in the future, we intend to follow the same protocol—providing notice to affected account holders and posting the requests publicly.

DMCA Takedown Notices

Many of the takedown requests we receive are notices submitted under the Digital Millenium Copyright Act, alleging that user content is infringing someone's copyright. Each time we receive a complete DMCA takedown notice, we redact any personal information and post it to a public repository.

DMCA Takedown Notices Received

Here are the total number of complete notices that we received and processed in 2014. In the case of takedown notices, this is the number of separate notices where we disabled content or asked our users to remove content:

  DMCA Totals.
  Takedown Notices: 258.
  Counter Notices or Retractions: 17.
  Notices of Legal Actions Filed: 0

  Total Number of DMCA Notices, Counter Notices and Retractions by Month
Incomplete DMCA Takedown Notices Received

From time to time, we receive incomplete notices regarding copyright infringement. When we do, we ask the submitting party to revise it to comply with the legal requirements. Usually they will respond with a revised notice, but occasionally, they may resolve the issue on their own without resubmitting a revised notice. We don't currently keep track of how many incomplete notices we receive, or how often folks are able to work out their issues without sending a takedown notice.

Projects Affected by DMCA Takedown Requests

We also tabulated the total number of projects (e.g., repositories, Gists, Pages sites) affected by each notice. Here is a graph showing the total number of affected projects by month:

  Total Number of Projects Affected by DMCA Notices, Counter Notices and Retractions by Month

Note, however, that on October 16, 2014 we made a change to our DMCA Policy that impacted that number. Before the policy change we would have counted each reported link to a repository as a single affected repository, even though it would have actually affected the whole network of forks. After the policy change, however, since we require the notices to specify whether any forks are infringing, the "affected" number should more accurately reflect the actual number of repositories implicated by the takedown notice. Though it is too early to properly gauge the effect of this change, we noticed that the average number of repositories listed on a takedown notice increased from 2.7 (for the period of Jan 1 - Oct 15) to 3.2 (for the period from Oct 15 to Dec 31). The median number of affected projects remained the same for both periods: 1.0.


We want to be as open as possible to help you understand how legal requests may affect your projects. So we will be releasing similar transparency reports each year. If you have any questions, suggestions, or other feedback, please contact us.

Announcing Git Large File Storage (LFS)

Distributed version control systems like Git have enabled new and powerful workflows, but they haven't always been practical for versioning large files. We're excited to announce Git Large File Storage (LFS) as an improved way to integrate large binary files such as audio samples, datasets, graphics, and videos into your Git workflow.

Git LFS is a new, open source extension that replaces large files with text pointers inside Git, while storing the file contents on a remote server like or GitHub Enterprise.


Git LFS is easy to download and configure, works on all major platforms, and is open sourced under the MIT license.

Early access to Git LFS support on

We're ready to roll out Git LFS support to a select group of users. If you'd like to be one of the first to try it out on, sign up for early access using your GitHub account.

In the next few months, every repository on will support Git LFS by default.


Every user and organization on with Git LFS enabled will begin with 1 GB of free file storage and a monthly bandwidth quota of 1 GB. If your workflow requires higher quotas, you can easily purchase more storage and bandwidth for your account.

Want to start working with large files on Sign up for early access.

Git Merge 2015 Approaches!

gitmerge graphic

Next week, we'll converge in Paris to celebrate 10 years of Git. Thank you for helping us raise funds that benefit the Software Freedom Conservancy.

We look forward to hanging out in the beautiful La Gaîté Lyrique on April 8-9. We've got Git experts from across the industry coming to discuss the future of Git with you.

If you haven't already, check out the complete speaker lineup and schedule, featuring speakers from Google, Twitter, Atlassian, Microsoft and more. The conferenced will be hosted by GitHub's own Scott Chacon.

On Thursday night we'll gather at the stunning La Cartonnerie to wish Git a happy tenth birthday with cocktails, snacks and entertainment.

There are only a few tickets left, so if you'd like to register, now is the time.

Social Coding Shirts now available in the Shop

Do you remember your first open source project? This shirt with an early GitHub motto will take you back to that first commit.

Social Coding Shirts

Get them in the GitHub Shop

Large Scale DDoS Attack on

We are currently experiencing the largest DDoS (distributed denial of service) attack in's history. The attack began around 2AM UTC on Thursday, March 26, and involves a wide combination of attack vectors. These include every vector we've seen in previous attacks as well as some sophisticated new techniques that use the web browsers of unsuspecting, uninvolved people to flood with high levels of traffic. Based on reports we've received, we believe the intent of this attack is to convince us to remove a specific class of content.

We are completely focused on mitigating this attack. Our top priority is making sure is available to all our users while deflecting malicious traffic. Please watch our status site or follow @githubstatus on Twitter for real-time updates.

Navigate branches from your phone

Branches are an essential part of collaborating using GitHub Flow. And it's now easier than ever to browse a repository's branches on your phone.

Using the new dropdown, you can access the recently active branches for a project or browse through all of its branches.


Scheduled Maintenance - Saturday 3/21/2015 @ 12:00 UTC

This Saturday, March 21st, 2015 at 12PM UTC we will be upgrading a large portion of our database infrastructure in order to further ensure a fast and reliable GitHub experience.

To minimize risk to customer data, the site will enter maintenance mode while the upgrade is performed. HTTP, API, and Git access to will be unavailable during this window, which we estimate will last no longer than 15 minutes. During the maintenance we will update our MySQL Server version, as well as move a large portion of our data to an isolated cluster. This will improve scalability and help sustain the growth of our data.

We will update our status page and @githubstatus at the beginning of maintenance and again when the maintenance is completed.

Introducing mobile web notifications

Web notifications on GitHub keep you apprised of the latest activity from the repositories you watch within your browser. With the addition of mobile web notifications, now you can stay up to date from your phone.

If you already use web notifications, you'll see a familiar indicator in the top right of every page whenever you have unread activity.

Mobile notifications

Use the switcher at the top of the page to filter your notifications. By default we show all your unread activity across the repositories you watch, but filtering to a specific repository—or even just the threads you're participating in—is just a couple taps away.

Switch contexts

When you want to skip a notification, you can always mark it as read. Tap the checkmark on the right of individual notifications and they're immediately updated. You can also use the link in each repository group's header to mark multiple notifications as read.

New to web or email notifications on GitHub? Head to your account settings to customize how and where you receive notifications for the repositories you watch.

PDF Viewing

We've been displaying 3D, map, and tabular files for a while now. We're now happy to add PDF documents to the list!

PDF being rendered

Simply browse to a PDF document and we'll render it in your browser like any other file. From presentations to papers, we've got you covered. Many thanks to Mozilla and every contributor to PDF.js. If you have any further questions, check out the help article.

The Game Has Changed

GitHub Game Off III

GitHub's Game Off is back, and this year it's a little different!

The Challenge

Take an existing game or game jam entry on GitHub, fork it and do something awesome with it. You can change the sprites, add a soundtrack, add a new level, port the game to a different platform, or... go plain crazy. Tackle it yourself or team up with some friends. Let your imagination run wild! The theme of the jam is... "the game has changed"!

You're encouraged to use open source libraries, frameworks, graphics, and sounds in your game, but you're free to use any technology you want. The only restriction is that the game should be web-based i.e. playable in a web browser.

We'll feature some of our favorite and most creative entries on the GitHub blog.

Where to start

GitHub is a goldmine of content when it comes to games. Take a look at the following resources to see if there's one you'd be intersted in forking and jamming on:

Please feel free to suggest others on Twitter using the hashtag #ggo15.


  • If you don't already have a GitHub account, sign up for a personal account now - it's free!
  • Be sure to follow @github on Twitter for updates.
  • Once you've found a game repository, fork it to your personal or organization GitHub account and get jamming!
  • Make sure your code is pushed to the default branch of your forked repository before April 13th at 13:37pm PDT!
  • Finally, fill out this short form and tell us about your entry by April 13th at 13:37pm PDT.

Comments / Questions / Help


Students, work on Open Source with GitHub this summer

GitHub has been selected to participate as a mentoring organization for Google Summer of Code, a program where students receive a stipend to contribute to open source projects.

If you want to work with a GitHubber on an open source project, check out our list of project ideas, featuring opportunities to contribute to the Atom Editor and the Homebrew package manager for OS X. If you have an idea for a project that we haven't suggested yet, browse GitHub's open source projects and open a new issue on the github/gsoc repository to suggest other ideas or ask questions about participating in the program.

Applications can be submitted to the Google Summer of Code website between March 16 and March 27.

Create Pull Requests in GitHub for Windows

Just like our Mac client, you can now use GitHub for Windows to submit pull requests to GitHub or GitHub Enterprise, right from your desktop.

Create a pull request

We didn't forget forks, either! If you fork a repository and then want to contribute changes to the upstream repository, GitHub for Windows will keep track of upstream branches. This means less hassle when you're ready to contribute your changes back.

Upstream branches

Download GitHub for Windows and start sending pull requests now!

OctoTales • Epic Games

We recently caught up with some of our friends at Epic Games in Cary, NC a few weeks ago to talk about the latest developments with Unreal Engine and Unreal Tournament. Since opening up the engine source code on GitHub a year ago, they've released seven major updates that incorporate an array of contributions from the community such as @SRombauts' git plugin and much improved Linux support.

Our latest OctoTale captured some of Epic Games' stories and some of the amazing work that's going on in their passionate vibrant community. We think you'll enjoy it.

And finally, some more exciting news for fans of the Unreal Engine: as of this week, developers can enjoy free access to Unreal Engine 4!