close
The Wayback Machine - https://web.archive.org/web/20110623090610/https://github.com/features/community

Features

The GitHub Community

835,157 developers

(and counting)

Photos by Sebastian Hillig, Claude Nix and Paul Campbell

Activity Streams Screenshot

Activity Streams

GitHub allows you to watch repositories and follow users to generate activity streams. Our activity streams show you everything important that’s happening with anyone or anything on GitHub.

Developer Profile Screenshot

Developer Profiles

Every developer gets their own profile page that is automatically updated with a stream of the important things they are doing on GitHub and a list of the Open Source projects they are hosting at GitHub. Many developers have started referring to GitHub Profiles as the new résumé.

Explore Screenshot

Explore GitHub

Explore is a section of our site where we highlight the most interesting and popular repositories on GitHub right now. Additionally, our comprehensive search helps you find repositories, users, and code across all of GitHub.

Meet the Network Graph

Forking is a good thing. We encourage developers to fork repositories often — even for the simplest changes. The network graph answers the question: What are people doing in those forks?

The network graph is available on every repository on GitHub. It gives you as a project maintainer an at-a-glance understanding of the activity on your source code across all developers interested in it.

Before GitHub, forking was a subgroup of developers going in a different direction with the codebase — a rift in the community. Today a project can have hundreds of forks, each trying out ideas that may get merged back in to the main project. Forks now represent a vibrant and active community.

Network Graph Screenshot
Fork Queue Screenshot

GitHub Fork Queue: Merge changes from the web

The network graph shows you what's happening in your forks, but the fork queue lets you merge these changes on the web. The Fork Queue is a list of all the commits in a repository's network and a visual indication of whether they will merge in cleanly.

Once you know a commit will merge cleanly, you can toggle a checkbox and click "Apply" to merge the changes into your repository. The Fork Queue is great for merging in quick changes on the go - it works great on iPhones, iPads and Android phones.

GitHub Meetups

We love our users — which is why we’re trying to meet as many of them as we can in meatspace. We try our best to host a GitHub Meetup in every city that we’re traveling to. Which is why we’ve had GitHub meetups in places like Amsterdam, Moscow, Boulder, Dublin, Paris, New York, São Paulo, Portland, Prague, Rio de Janerio, Portland, Belfast, Chicago, Sydney, Philidelphia, and dozens of other cities around the world.

Next time we’re in your city, be sure to keep an eye on our blog and twitter feeds to see where we’ll be hosting the next GitHub meetup. Let us buy you a beer and geek out with fellow GitHub enthusiasts.

Don't forget to check out our GitHub meetup flickr group to see what a GitHub meetup looks like.

A taste

Markdown Cheat Sheet

Format Text

Headers

# This is an <h1> tag
## This is an <h2> tag
###### This is an <h6> tag

Text styles

*This text will be italic*
_This will also be italic_
**This text will be bold**
__This will also be bold__

*You **can** combine them*

Lists

Unordered

* Item 1
* Item 2
  * Item 2a
  * Item 2b

Ordered

1. Item 1
2. Item 2
3. Item 3
   * Item 3a
   * Item 3b

Miscellaneous

Images

![GitHub Logo](/images/logo.png)
Format: ![Alt Text](url)

Links

http://github.com - automatic!
[GitHub](http://github.com)

Blockquotes

As Kanye West said:
> We're living the future so
> the present is our past.

Code Examples in Markdown

Syntax highlighting with GFM

```javascript
function fancyAlert(arg) {
  if(arg) {
    $.facebox({div:'#foo'})
  }
}
```

Or, indent your code 4 spaces

Here is a Python code example
without syntax highlighting:

    def foo:
      if not bar:
        return true

Inline code for comments

I think you should use an
`<addr>` element here instead.