• Twitter Service Hooks Return

    atmos 8 Sep 2010

    A few weeks back twitter removed basic auth support and as a result many of you haven't been receiving twitter notifications for changes to your repositories. We've taken the the necessary steps to re-enable this service via their OAuth based API. All you need to do is edit your repository and click on the link to get an OAuth token.

    Click on the OAuth Link

  • The Reverse Twitter Effect

    defunkt 1 Sep 2010

    While Twitter may see traffic spikes during Apple events, we see quite the opposite:

  • Pull Requests 2.0

    rtomayko 31 Aug 2010

    GitHub launched with a simple pull request system on day one. You've used it to send 200 thousand pull requests in just over two years. Now we're taking it to the next level with a re-imagined design and a slew of new tools that streamline the process of discussing, reviewing, and managing changes.

    As of today, pull requests are living discussions about the code you want merged. They're our take on code review and represent a big part of our vision for collaborative development.

    Know What You're Sending

    Sending a pull request is simple. Browse to the branch or commit with your recent work and hit the Pull Request button. You'll be greeted by a brand new screen:

    Pull requests are now fully revision aware and take into account not only what you would like pulled but also where you intend those changes to be applied. They even work when sending from and to the same repository, making pull requests just as useful in scenarios where a team is working out of a single shared repository as they are in the fork + pull model.

    When you send a pull request, you're starting a discussion.

    Some back and forth is typically required before a pull request is accepted. The maintainer needs clarification, or the change doesn't conform to the project's coding conventions, or maybe someone was able to take a concept 80% to completion and needs help working through the last bits.

    The discussion view makes pull requests the best place to have these types of conversations. Anywhere. Here's why:

    The discussion view presents all pull request related activity as it unfolds: comment on the pull request itself, push follow up commits, or leave commit notes - it's all interleaved into the discussion view as it happens.

    Revision Aware

    The discussion view is perfect for watching changes evolve over time, but it's equally important to know exactly what modifications would be made if the changes were accepted right now. The Commits and Files Changed tabs are quickly accessible and show the cumulative progress of the pull request:

    Look familiar? It's a miniature compare view.

    Visible, Linkable, Archived

    Anyone with access can browse a repository's pull requests by visiting the repository's Network ⇢ Pull Requests page.

    Every pull request has a URL so you can link to them. They're archived forever and indexed by search engines.

    An Issue at heart

    Pull requests are tightly integrated into GitHub Issues. When you see an [^] icon in the issues list, it means there's a pull request attached.

    Don't use Issues? No problem. You still get awesome pull requests.

    Pull Request Dashboard

    The pull request dashboard gives a high level view of all pull requests across every repository you or your organization is involved with.

    What are you waiting for?

    Pull requests sent prior to today are not automatically imported into the new system. If you have outstanding requests, use them as an opportunity to try out revision aware pull requests today!

  • Corey Donohoe is a GitHubber

    defunkt 30 Aug 2010

    Today marks Corey "atmos" Donohoe's first day as a GitHubber. He'll be helping us make GitHub more awesome.

    We're all super excited to have Corey on board, and a quick browse through his repos explains why: Sinatra, node.js, and OAuth are among his interests. He has some amazing dogs, too.

    Also OS X - if you like the sound of homebrew and chef you'll definitely want to check out his cider project.

    You can follow him on GitHub, twitter, tumblr, or at his blog.

    Welcome to the team, Corey!

  • Mozilla Labs on GitHub

    defunkt 26 Aug 2010

    Mozilla Labs is now mirroring open source to GitHub: http://github.com/mozillalabs

    Read the blog post or check out the repositories on GitHub.

    Rumor has it we'll being see more from Mozilla on GitHub in the future, too!

  • Git Notes Display

    schacon 25 Aug 2010

    I just blogged about the new git-notes functionality over at the Pro Git blog. If you're interested in using Git notes for something, you might be interested to know that GitHub now supports them and will display them on your commit pages.

    If you push notes to GitHub, you will be able to see them at the bottom of the diff when you are viewing that commit. These are separate from GitHub commit comments and are displayed differently. The will look like this:

    To learn more about Git notes, read my post. on them, but the short of it is: they're cool for appending notes from automated systems (like ticket or build systems) but not really for having interactive conversations with other developers (at least not yet). Hope you find them useful.

  • Jekyll puts on SmartyPants

    mojombo 24 Aug 2010

    I just released and deployed Jekyll 0.7.0 to GitHub Pages today. This release includes support for SmartyPants via RDiscount for Markdown files. To get all those nice curly quotation marks, em/en dashes, and elipses, simply make sure your Jekyll repo's _config.yml contains the following lines:

    markdown: rdiscount
    rdiscount:
      extensions: [smart]
    

    Then, push your repo to GitHub and enjoy some automatic fancy typographical elements!

    NOTE: SmartyPants will only be active on pages written with Markdown.

  • Grails y Git en Español

    defunkt 19 Aug 2010

    kinisoftware ha creado un vídeo en español explicando como preparar un entorno de desarrollo Grails utilizando también Git (con GitHub en remoto) y SpringSource Tool Suite.

    kinisoftware gracias!

  • iOSDevCamp 2010 This Weekend

    defunkt 18 Aug 2010

    iOSDevCamp 2010 is being held at the PayPal headquarters in San Jose, California this weekend.

    What is it? Straight from the horse's mouth:

    iOSDevCamp (previously know as iPhoneDevCamp and iPadDevCamp) is an annual not-for-profit gathering to develop applications for iOS, including iPhone, iPad, and iPod touch, using both the native SDK and web standards.

    I'll be there Saturday — say hi if you're attending!

  • GitHub Meetup SF #21

    Lets do this meetup thing.

    The Facts:

    Benders Bar 806 S Van Ness Ave (between 19th& 20th St) Thursday, August 19th 2010 8:30pm

  • Ottawa Drinkup Tonight

    schacon 14 Aug 2010

    I'm currently at the FOSSLC conference in Ottawa, CA and we're going out to Dantessa Italian Bar tonight starting at 21:00 (9pm for us Americans). GitHub will be buying a round or two, so come meet the FOSSLC attendees who will be newly imbued with amazing tech knowledge and share some beer with us.


    View Larger Map

    Hope to see you there!

    Details: Dantessa Italian Bar
    131 Cooper Street Ottawa, Ontario
    9:00pm (21:00)

    Punch the guy wearing the short sleeved collared brown shirt if you're having a hard time getting a free beer

  • Design updates

    kneath 13 Aug 2010

    Earlier today we rolled out a minor design update to the site. Notably, we have a brand new home page (remember, you can always get to the homepage at http://github.com/home):

    It's simpler, sweeter and to the point. GitHub has evolved a lot since launch – and we've been bad at explaining that to newbies. Hopefully this is the first step of many to better explain our offerings.

    You'll also notice a new footer and language switcher:

    Did you know we also offer Training?

    For the astute, you'll notice lots of CSS improvments (only down to one image-based gradient!).

    Hope you all enjoy!

  • Making GitHub More Open: Git-backed Wikis

    We've been hearing a lot of great feedback regarding our current wiki system. Today, we're launching the first phase in a rollout of a completely rewritten Git-backed wiki system to address these issues. Each page is a file in a directory. Each change is a commit.

    Where's Markdown support?

    A lot of people like Textile, but wikis are one of the few places that don't support Markdown. The new GitHub Wikis leverage our markup library to support eight formats, with context sensitive help and a toolbar.

    Git-Powered History and Comparisons

    Being able to see diffs of changes is another highly requested feature for wikis. Git is pretty good at this already, so we just use the existing tools for showing the history and making comparisons.

    Images and Folders

    You can now reference images hosted inside the Git repository.

    Importing and Exporting

    Each wiki is a Git repository, so you're able to push and pull them like anything else. Each wiki respects the same permissions as the source repository. Just add ".wiki" to any repository name in the URL, and you're ready to go.

    View Your Content Locally

    We're also releasing Gollum, the same ruby library that powers GitHub Wikis. Gollum provides a ruby API for accessing and modifying your content, and also includes a small Sinatra web server. Clone the demo wiki to see what's available, or check out the Gollum readme for more detailed information.

    Our hope is that our community can help us make GitHub Wikis better, in the same way you've all helped us make GitHub Pages better through Jekyll. If other language implementations pop up, and other Git hosts start supporting Gollum Wikis, that'll be better for the Git community as a whole.

    Where's the Script?

    We've decided to improve the public wiki experience by hosting everything under the main github.com domain. To do this, we've had to sanitize all javascript and CSS in the wikis. You will no longer appear to be logged out when reading wikis for open source repositories.

    How Can I Upgrade?

    The new GitHub Wikis are still technically beta. We're encouraging our users to upgrade wikis on their own, and report any incompatibilities that come up. You're able to upgrade without disturbing the existing wiki. Once your new wiki is ready to go, you can disable the classic wiki, and we'll redirect traffic for you.

    We're looking at disabling all classic wikis and forcing upgrades starting September 12th.

  • GitHub Jobs

    defunkt 10 Aug 2010

    You all know about GitHub Jobs by now, so we thought we'd kick off the official launch by highlighting some cool jobs we've found in the past seven days.

    Some of Our Favorites

    Futuristic Stuff

    Cool Companies

    Drupal Engineers for Acquia:

    We think developers who want to work on the best, most dynamic, and most interesting open-source web technology project on the planet have no better place to work than here – working on Drupal.

    Software Engineer (Scala) for Remember the Milk:

    Did you fall in love with Scala at first sight? Do you dream of actors, DSLs, implicits and pattern matching?

    Machine Learning Specialist for Hello, Chair Inc:

    Essentially, we want you to enter a Netflix Prize-esque competition against yourself.

    And tons more on GitHub Jobs!

  • Boston Drinkup Tonight!

    schacon 10 Aug 2010

    Sorry for the last minute notice, but GitHub will be buying beer for geeks at Flat Top Johnny's in Cambridge tonight (Tuesday, August 10th) around 9:30. We're piggybacking on the bostonrb after party, so come mix and mingle. I may even get a couple LinuxCon geeks to come out with us, which is why I'm here in the first place.

    Also, even though PJ won't be there, it is his birthday so come and celebrate it as it was meant to be celebrated!


    View Larger Map

    Where and When:

    1 Kendall Sq
    Cambridge, MA 02139
    9:30p, Tues Aug 10th