340 likes | 814 Views
GitHub. Not Just Git. By: Travis Osteen Rebecca Roberts Sean Hickman. Outline. What GitHub adds to Git Why use GitHub? Social Programming GitHub Flavored Markdown Issues / Comments / Milestones GitHub’s Users Future of GitHub Demo. Git + Hub.
E N D
GitHub • Not Just Git By: Travis Osteen Rebecca Roberts Sean Hickman
Outline • What GitHub adds to Git • Why use GitHub? • Social Programming • GitHub Flavored Markdown • Issues / Comments / Milestones • GitHub’s Users • Future of GitHub • Demo
Git + Hub • GitHub is a visual front-end for Git • GitHub brings a social aspect to Git
Different Interfaces • Different interfaces for accessing GitHub include: • Web Browser (Desktop and Mobile) • Mobile Apps • Official Android app • 3rd party iOS and Windows Phone apps • Desktop Apps (Windows or Mac)
Distribution and Collaboration • Allows you to work visually with others • Issues • Comments • Speeds development and increases productivity
Social Programming • Lowers barrier to entry for open source development • Others can see your work • Headhunters look at GitHub • usage and activity
Account Creation • Free account for public repositories • Paid account for private repositories • Free school account for private repositories • Enterprise accounts for self-hosted repositories
Collaboration • Syncing will get and put • Pull requests • Issue resolution • Forking and Merging
Issues and Milestones • GitHub issues allow for bug-tracking and feature discussion • Assign issues to particular contributors • Group and tag issues by kind, feature and milestone • Group of features closed before milestone met
GitHub Flavored Markdown(GFM) • Markdown(.md) with processing • code highlighting • easy header tags, tables, syntax highlighting, bold, italic, block-quotes, lists, etc… • inline HTML • Simplified intra-site links • Available in issues, comments and files
Worth mentioning • Gists: Code snippets that are versioned, forkable and git-based. Can be private or public. • Pages: A webpage for your repo. Can be automatically generated from a Readme.md • Wiki: Per-repository and useful for documentation, usage examples, etc…
The Future of GitHub • Emphasize enterprise, paid services • Encouraging users to license their projects • Collaboration on non-software projects • books, hardware projects, schematics for circuit boards, legal documents--anything that ends up in a digital format
Who uses GitHub • Over 4 million users, “several hundred thousand” paid users • Open-source developers, “casual forkers”, 77% of projects have no license • Enterprise clients: Lockheed Martin, Microsoft, LivingSocial, VMware, Walmart … • Instances of GitHub licensed to run on a company’s servers • Find open-source material on GitHub, integrate with proprietary material privately
Repository Creation • Create a repository within the GitHub interface • Push a local, possibly empty, git tree to GitHub
Creating a GitHub Repository • Create an empty repo on GitHub
Creating a GitHub Repository • Copy the clone URL
Creating a GitHub Repository • In a local directory: • gitinit • git add . • git commit -m `initial commit` • git remote add origin url • git pull origin master • git push origin master
References • github.com • http://stackoverflow.com/questions/4658606/import-existing-source-code-to-github • https://github.com/blog/1715-faster-more-awesome-github-pages • https://github.com/blog/1672-introducing-github-traffic-analytics • https://github.com/blog/1627-github-enterprise-11-10-320-release