Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Everything I wish I knew when I started using G...

Brent Beer
July 23, 2015
7.3k

Everything I wish I knew when I started using GitHub

Everyone can find something useful on GitHub, whether it’s to learn about some new framework, contribute to open source, or collaborate on an internal project. If you haven’t used it for a while, you may not be leveraging everything it has to offer. What you need is a good explanation of these features you wish you had on your first day.

We’ll start out looking at some features that will help enhance your view of the entire ecosystem; and we’ll dive into strategies for extending GitHub to make your projects work better not only for you, but for your entire team. You will walk away from this talk with all the information you need to use every inch of GitHub on your own and with your colleagues.

Read more at: http://www.oscon.com/open-source-2015/public/schedule/detail/43710

Brent Beer

July 23, 2015
Tweet

Transcript

  1. the best way to build and ship software Everything I

    wish I knew when I started using GitHub
  2. the best way to build and ship software Everything I

    wish I knew when I started using GitHub
  3. ! the best way to build and ship software !

    " 3 BRENT BEER SALES ENGINEER Who am I?
  4. the best way to build and ship software But wait

    a second, let’s chat: Why open source? 4 #
  5. the best way to build and ship software But wait

    a second, let’s chat: Why open source? 5 #
  6. $ the best way to build and ship software Largest

    Subversion Host 6 % SVN HUB! If you have people coming over from SVN, it may be easier to just have them use their existing commands to get their project over.
  7. $ the best way to build and ship software Easy

    URL Sharing 8 & GIT.IO URL SHORTENER Ever wish you had a smaller URL to share with your coworkers?
  8. $ the best way to build and ship software Pull

    Requests as Patches 10 ' .PATCH Adding a .patch to your pull request URL will generate a formatted patch.
  9. $ the best way to build and ship software Pull

    Requests as Patches 11 ' .PATCH Adding a .patch to your pull request URL will generate a formatted patch.
  10. $ the best way to build and ship software Pull

    Requests to Anyone! 12 ' REPOSITORY NETWORK You don’t just have to send the PR to the parent repository.
  11. $ the best way to build and ship software Closing

    Issues from Pull Requests 14 ' CLOSE THE ISSUE FROM THE PULL REQUEST Some people know you can close an issue or pull request from a commit message, but you can do this in the web.
  12. $ the best way to build and ship software Gists

    16 ( FULL GIT REPOSITORY Gists aren’t just place to drop a nice easy sharable file. They’re full git repositories
  13. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 18 ) INVESTIGATE A FILE AND A COMMIT If you don’t know how to use blame from command line, that’s fine. Finding things in the web can be easier.
  14. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 19
  15. $ the best way to build and ship software Licenses

    and Line Comments 20 * QUICKLY CREATE A LICENSE OR COMMENT ON SPECIFIC LINES Creating a LICENSE fast and easy is important for all true open source projects. Commenting on specific changes is equally important for review
  16. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 21
  17. $ the best way to build and ship software Revert

    Pull Requests 22 ' PULL REQUEST DIDN’T GO AS PLANNED? REVERT! Sometimes our features don’t work as we intended and we need to undo them. Don’t bother leaving the UI, revert the whole feature right now.
  18. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 23
  19. $ the best way to build and ship software Task

    List 24 ' TRACKING ISSUES An issue that keeps track of other sub tasks is a great way to work on small pieces of code
  20. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 25
  21. $ the best way to build and ship software Rendering

    Files 26 + VIEWING NON-CODE FILES ON GITHUB IS IMPORTANT GitHub doesn’t just have to contain your code. It can include your images, geojson maps, 3d files, and even pdfs
  22. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 27
  23. $ the best way to build and ship software Explore

    and Newsletter 28 , EXPLORE REPOSITORIES AND GET EMAIL UPDATES Finding new projects on GitHub can be done from our explore section. You can also find other users to find to make your newsletter more complete.
  24. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 29
  25. $ the best way to build and ship software Global

    Issues and Pull Request 30 - ALL YOUR ISSUES AND PULL REQUESTS IN ONE PLACE You may work on many projects and you may have few projects open. They’re easy to access from a single screen.
  26. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 31
  27. $ the best way to build and ship software Atom

    32 ( OPEN SOURCE TEXT EDITOR Atom is open source all the way down. Down to a project even called Electron (electron.atom.io) that helps you build desktop clients.
  28. $ the best way to build and ship software Atom

    33 ( OPEN SOURCE TEXT EDITOR Atom is open source all the way down. Down to a project even called Electron (electron.atom.io) that helps you build desktop clients.
  29. $ the best way to build and ship software Web

    Blame and Linked Pull Request Information 34
  30. the best way to build and ship software What new

    feature or tool are you going to use today? 35 ?