gotta get
(and )
Stephanie Datu
why should I get ?
Remembers changes to a file or set of files
over time so that you can recall specific
versions later
Te...
why should I get ?
Easy team collaboration
Public and private code backup
Watch the activity on a repo
Follow streams or d...
in groups
in association with
$ git clone https://github.com/username/repo.git
+ remote repo named origin pointing to the ...
in groups
in association with
understand changes better:
pretty logs
$ git log
$ git log ­­oneline
$ git log ­­pretty=format:”%h %cn %cD %s”
$ git log ­­pretty=format:
●
%H: commit hash
●
%h: abbreviated commit hash
●
%an: author name
●
%ae: author email
●
%aD: a...
best practices
Commit early and commit often
Commit related changes
Don't commit half-done work
TATFT especially...
Before...
Thanks!
●
Follow me on GitHub:
https://github.com/stephdatu
●
Follow me on twitter: @StephShutUp
●
Connect with me on Link...
Upcoming SlideShare
Loading in...5
×

gotta get git (and github)

761

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
761
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

gotta get git (and github)

  1. 1. gotta get (and ) Stephanie Datu
  2. 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. 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. 4. in groups in association with $ git clone https://github.com/username/repo.git + 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. 5. in groups in association with
  6. 6. understand changes better: pretty logs $ git log $ git log ­­oneline $ git log ­­pretty=format:”%h %cn %cD %s”
  7. 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. 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. 9. Thanks! ● Follow me on GitHub: https://github.com/stephdatu ● Follow me on twitter: @StephShutUp ● Connect with me on LinkedIn: http://www.linkedin.com/in/sdatu ● Email me: stephdatu@gmail.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×