Subscribe

GitHub Universe

The event for people building the future of software, September 13-15 in San Francisco. Learn more

Diffable, more customizable maps

We're excited to announce two improvements to mapping on GitHub today: diffs and feature-level customizations.

Visualizing changes over time

We added the ability to visualize geospatial data to GitHub last summer, but the true value of version control comes not from where your information is now, but how it's changed over time, and where others propose it should be.

Starting today, any time you view a commit or pull request on GitHub that includes geodata, we'll render a visual representation of what was changed. For example, here's a diff of Illinois's famed 4th congressional district after undergoing redistricting in 2011:

Illinois 4th Congressional district

We'll even diff properties within the geometry when they change:

Updating a property

Customizable maps

We've also made some changes under the hood to make mapping geoJSON files on GitHub faster and more customizable.

In addition to more-responsive, retina-ready maps, you can now customize individual features by specifying properties such as the fill color or opacity within the geoJSON file itself like the National Park Service did here:

simple style spec

We've implemented version 1.1.0 of the open simplestyle specification, so be sure to check out the full documentation for the details.

Happy collaborative mapping!

GitHub Security Bug Bounty

Our users' trust is something we never take for granted here at GitHub. In order to earn and keep that trust we are always working to improve the security of our services. Some vulnerabilities, however, can be very hard to track down and it never hurts to have more eyes.

We are excited to launch the GitHub Bug Bounty to better engage with security researchers. The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our responsible disclosure process. Then, to recognize the significant effort that these researchers often put forth when hunting down bugs, we reward them with some cold hard cash.

Bounties typically range from $100 up to $5000 and are determined at our discretion based on actual risk and potential impact to our users. For example, if you find a reflected XSS that is only possible in Opera, which is < 2% of our traffic, then the severity and reward will be lower. But a persistent XSS that works in Chrome, which accounts for > 60% of our traffic, will earn a much larger reward.

Right now our bug bounty program is open for a subset of our products and services (full list is on the site), but we are already planning on expanding the scope as the things warm up.

Check out the GitHub Bug Bounty site for full details, and happy hunting!

Announcing Guides

Today we're announcing something new: GitHub Guides.

GitHub Guides

We've got four guides up right now:

Guides are designed to help with concepts that are a bit too difficult to sum up with a simple Google search. Much like our GitHub Guides channel on YouTube, the new site will focus more on workflows and project communication rather than bits and bytes and stack traces.

This is just the start for Guides. Check back every now and then as we add more tutorials and writeups about using Git and GitHub.

Enjoy!

Redesigned Conversations

Today we're excited to ship redesigned conversations on GitHub. Here's an example:

GitHub conversations

More meaningful conversations

Scanning and working with all the content available in conversations—replies, CI status, commits, code review comments—is now easier than ever.

convos-ship-pull-request-events

Comments now stand out as the most important elements in a conversation. Comments that you make are also highlighted blue. Anything that isn't a comment—like commits or issue references—has been subdued to better differentiate content. All of these changes come together to help you focus on what matters most in a particular conversation.

Streamlined layout

We've consolidated and moved management tools for Issues and Pull Requests into the sidebar. Add or remove labels, update milestones, subscribe to notifications, and assign people within one spot. Also, you can now manage labels directly on Pull Requests.

Additionally, titles and state indicators (open, closed, or merged) have been moved to a more prominent header to quickly and easily identify the Issue or Pull Request you're viewing.

convos-ship-pull-request-header

See the new conversations today in one of your favorite GitHub repositories.

Better Organizations

Today we’re making it easier to manage GitHub organizations. Whether your organization is a large private company or a small open source project, these improvements will help keep your teams organized and your code secure.

An improved profile

Organization owners can now add members and teams right from the organization’s profile.

profile

Members

Owners now have a unified list of all members. To help you stay secure, private organization owners can also see which members have two-factor authentication disabled.

members

Teams

You can quickly search and manage teams you belong to. We’ve also made it even easier to leave your teams.

teams

Teams are the best way to limit access to your organization’s repositories, so we made the team page fast and simple.

team

Enjoy!

Remember, teams aren’t just for access control! You can bring teams into a conversation with team mentions. Keep your feedreader pointed here to stay up to date with what comes next.

Closed Captions on YouTube

With help from the non-profit, open-source project Amara, we've added English closed captions to all of our videos on YouTube. This includes all videos on the main GitHub channel (such as OctoTales, Passion Projects, and the Better Together music video), as well as videos on the GitHub Guides channel (such as the GitHub Foundations series).

More Languages

We've also started to expand our accessibility to other languages. For instance, the Foundations series now has Japanese captions. Here's how you enable them:

yt-cc-japanese

Translations Needed

We think it would be cool if people all over the world could enjoy our videos, regardless of what language they speak. So, starting today, we're inviting anyone who's interested to help us translate our videos via Amara's Volunteer Platform.

If you'd like to help, go to the GitHub team on Amara and select "Join Team." (If you don't have an account, you can create one or sign-in via your preferred social network.) Then you'll see the videos available for translation, and you can use Amara's slick in-browser subtitling tool to add your translation. Thanks and cheers to accessibility! 🍺

Web-flow editing from Pull Requests

Pull Requests are key to our collaboration workflow here at GitHub, so today we’re making it a little easier to stay in the flow of a PR while collaborating directly on the web.

When viewing the "files changed" tab of any PR, people with push access to the repository will be able to edit or view files directly on the PR’s branch. Once you’ve made your change, you’ll be sent straight back to the PR’s diff to continue the review.

2014-01-10 at 11 46 am

The buttons will always link to the latest version of each file on the branch, enabling rapid-fire web-based iteration and discussion without having to leave the context of the PR.

Enjoy!


ProTip™: If you’re viewing a branch’s version of a file, and want a canonical link that will always point to this specific version of the file (even if the branch changes it further), hit the y key on your keyboard, and the page’s URL will change to use the SHA of the latest commit on the branch instead.

New Year, New CEO for GitHub

It's a brand new year, and each year calls for reflection on where we've been, where we're going, and how each of us here at GitHub can best focus our talents and energy. To kick off 2014 I've asked my long-time friend and GitHub cofounder, Chris Wanstrath, to take the role of CEO. In this role, Chris will be responsible for leading the company, defining our vision, and working with our amazing team to establish and execute the strategies necessary to achieve our most ambitious goals.

I'll continue to work closely with Chris on vision, strategy, and execution in the role of President of GitHub. This shift will allow me to take responsibility for R&D and new growth opportunities within the company. I'll also be thinking deeply about how we can continue to optimize for happiness as we grow, and will remain the company's public champion and primary spokesperson.

We tend to do things differently here at GitHub, and remaining fluid in how we define our roles is a big part of that. In fact, Chris and I have stepped into these roles over the past few months and today we're simply acknowledging the change publicly. While we don't use titles heavily at GitHub, we think in this case they're useful to communicate areas of responsibility both internally and externally.

2014 is going to be an exciting year. I, for one, can't wait to see what happens!

Tom Preston-Werner
Cofounder & President, GitHub, Inc.

The CEO is President. Long live the CEO!

Faster, More Awesome GitHub Pages

We just rolled out some big improvements to GitHub Pages. Now, when someone visits a Pages site, rather than GitHub serving the content directly, the page is served by a global Content Delivery Network, ensuring that the nearest physical server can serve up a cached page at blazingly fast speeds. As an added bonus, we can now protect your GitHub Pages site with the same kind of Denial of Service mitigation services used for GitHub.com.

If you are using a subdomain, custom subdomain, or an A record with GitHub Pages, you may need to make some changes.

Default User Domain - username.github.io

Default subdomains are automatically updated by our DNS, so we've got you covered.

Custom Subdomain (www.example.com) - with CNAME

If you are using a custom subdomain (like www.example.com), you should use a CNAME record pointed at username.github.io as described in our help article.

Apex domain (example.com) - with ALIAS or A

If you currently use an A record, you can tell if you need to move if your A record is pointed to 207.97.227.245 or 204.232.175.78. You can check using:

$ dig example.com
example.com.    7200  IN  A 207.97.227.245

OR

$ dig example.com
example.com.    7200  IN  A 204.232.175.78

Some DNS providers (like DNSimple) allow you to use an ALIAS record to point your custom apex domain to username.github.io. If your DNS provider supports this configuration, it will allow us to provide the full benefits of our Content Delivery Network and Denial of Service protection to your Pages site.

If you switch to a subdomain or switch to a DNS provider that supports ALIAS records, you can take advantage of the Content Delivery Network and Denial of Service mitigation.

If you are using an apex domain (e.g. example.com) instead of a subdomain (e.g. www.example.com) and your DNS provider does not support ALIAS records, then your only option is to use A records for your DNS. This configuration will not give your Page the benefit our Content Delivery Network, but you will still be protected by our Denial of Service mitigation. Configure your A or ALIAS records as described in our help article.

Happy (and faster) publishing!

Introducing GitHub Traffic Analytics

The holidays are over and we're getting back into the shipping spirit at GitHub. We want to kick off 2014 with a bang, so today we're happy to launch Traffic analytics!

You can now see detailed analytics data for repositories that you're an owner of or that you can push to. Just load up the graphs page for your particular repository and you'll see a new link to the traffic page.

traffic-link2

When you land on the traffic page you'll see a lot of useful information about your repositories including where people are coming from and what they're viewing.

github traffic

Looking at these numbers for our own repositories has been fun, sometimes surprising, and always interesting. We hope you enjoy it as much as we have!

10 Million Repositories

What an incredible and productive year! A few days ago the 10 millionth repository was created on GitHub.com, just in time for the new year.

The first million repositories were created in just under 4 years; 3 years, 8 months and 15 days to be exact. This last million took just 48 days. In fact, over 5.5M repositories — more than half of the repositories on the site — were created this year alone.

To celebrate, here's a look at some of the popular, interesting, and noteworthy projects that came online in 2013:

Here's a quick 📈 showing the path to 10M:

We'll be sharing some more stats from the year soon, but for now, happy holidays and here's to the next 10 million!

GitHub Pages just got easier

Today we're rolling out a reimagined pages.github.com, focused on helping you quickly and easily publish your first GitHub Pages site.

Screen shot of pages.github.com

Many sites you visit on a daily basis, from Bootstrap to developer.github.com, are hosted on GitHub Pages. The service lets you host your own static HTML5, CSS, and JavaScript sites via GitHub.

Now, pages.github.com will walk you through the steps of publishing your first site in minutes, whether it's via Git for command line, GitHub for Windows, or GitHub for Mac.

Example step on pages.github.com

For GitHub Pages veterans, we've also taken the opportunity to surface some great GitHub Pages resources to learn how to take advantage of the Jekyll templating engine, for example, or how to set up a custom domain.

Happy publishing!

More Explore Features

We've drafted your friends to help you find even more interesting projects with a new module on GitHub Explore. You'll now see stars from people you follow on the explore landing page, the mobile version, and the explore newsletter.

Starred by people you follow

Starred by people you follow

You can see which of your friends starred it by clicking the stars number on the right side of the repository.

Friends who starred

Starred by GitHub staff

We've had as much fun using the new GitHub Explore as we've had building it. We're sharing the repositories we've discovered in the new Starred by GitHub staff section.

Starred by GitHub staff

Soft-wrapping on prose diffs

Starting today, diffs on prose documents are soft-wrapped.

Before:

hard-wrapped diff

After:

Soft-wrapped prose diff

Review without scrolling, comment with ease, and stop hard-wrapping your prose documents.

Descriptive error messages for failed GitHub Pages builds

It's tough to be the bearer of bad news. Fortunately, today we're making it a bit easier to quickly publish beautiful pages for you and your projects.

When you push a change to your GitHub Pages site — whether via Git command line, one of the desktop apps, or GitHub.com — we email you if for any reason we can't build your site.

Starting today, you'll also get a descriptive, human-readable error message for any failed build so that you can more easily troubleshoot what went wrong:

example failed build email

We've started by supporting the most common error messages seen on GitHub Pages, and will continue to roll out support for additional errors in the coming weeks.

For more information on troubled builds, see the Jekyll troubleshooting guide or contact GitHub Support. Happy publishing!