Your SlideShare is downloading. ×
  • Like
gotta get git (and github)
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

gotta get git (and github)


My first lightning talk on the benefits of using git and github in a team environment!

My first lightning talk on the benefits of using git and github in a team environment!

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. gotta get (and ) Stephanie Datu
  • 2. why should I get ? Remembers changes to a file or set of files over time so that you can recall specific versions later Team-centric in nature Who made what changes When they were made How the changes differ Why they were changed Local or Remote Easy to learn!
  • 3. why should I get ? Easy team collaboration Public and private code backup Watch the activity on a repo Follow streams or developers See the activity done on forked repos Easy access allows for global collaboration As a developer, GitHub acts as an portfolio of your work!
  • 4. in groups in association with $ git clone + remote repo named origin pointing to the repo the clones comes from + remote branches named origin/<branch­name> pointing to the cloned branches $ git checkout ­b <branch­name> $ git status $ git add . $ git commit ­m “Denote changes made” $ git commit ­a ­m “Denote changes made” $ git checkout master $ git merge <branch­name> $ git push
  • 5. in groups in association with
  • 6. understand changes better: pretty logs $ git log $ git log ­­oneline $ git log ­­pretty=format:”%h %cn %cD %s”
  • 7. $ git log ­­pretty=format: ● %H: commit hash ● %h: abbreviated commit hash ● %an: author name ● %ae: author email ● %aD: author date ● %ar: author date, relative ● %cn: committer name ● %ce: committer email ● %cd: committer date ● %cD: committer date ● %cr: committer date, relative ● %s: subject
  • 8. best practices Commit early and commit often Commit related changes Don't commit half-done work TATFT especially... Before committing After cloning/pulling Write good messages Use branches Agree on a workflow $ git help <command>
  • 9. Thanks! ● Follow me on GitHub: ● Follow me on twitter: @StephShutUp ● Connect with me on LinkedIn: ● Email me: