Quick and easy way to get started with Git & GitHub

  • 2,330 views
Uploaded on

(This is a session planned to be taken in Coimbatore .Net User Group(dotnetcbe.com) on sunday 13-oct-2013) …

(This is a session planned to be taken in Coimbatore .Net User Group(dotnetcbe.com) on sunday 13-oct-2013)
In this session I will talk about the simplest and quickest set of steps needed for getting started in Git & GitHub.

- I will talk a little about the concepts of Git & GitHub
- How to use “GitHub for Windows” and setup a GitHub based distributed source control system
- How Open Source projects on GitHub works

More 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

Views

Total Views
2,330
On Slideshare
0
From Embeds
0
Number of Embeds
6

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • https://help.github.com/articles/using-pull-requests
  • https://help.github.com/articles/using-pull-requests

Transcript

  • 1. Ashoka R K T Accompanying text article at http://c-smil.es/githubarticle Quick and easy way to get started with Git & Github blog: codeSmiles.com @ashoka_rkt
  • 2. Intro • Git is DRCS – Distributed Revision Control System • Git is fast • Created by the Linux team • This session will mostly focus on GitHub
  • 3. Why Distributed? • Each clone is a repository, it contains all the code and version history • Repository is present in all clients when it is cloned, so server crash doesn’t affect much • Each client is a backup of the server’s repository, which also contains file version history
  • 4. GUI vs CUI • GUI is simple with GitHub for Windows or • CUI is complex, like: $ git clone git://github.com/ashoka_rkt/dir
  • 5. The Git & GitHub Jargon • pull • push • Git’s commit vs conventional check in • staged changes • clone • fork • pull request • pull vs pull-request • merge pull-request to main repo
  • 6. Git Repository • Repository  Project • Your files will be here • Local repository & online repository • In GitHub it is present online • Another such site called BitBucket, has free private repositories
  • 7. Creating Repositories
  • 8. Creating Repositories
  • 9. Setting up your system
  • 10. Setting up your system
  • 11. Setting up your system
  • 12. Setting up your system
  • 13. Setting up your system
  • 14. Setting up your system
  • 15. Setting up your system
  • 16. Setting up your system
  • 17. Setting up your system
  • 18. Setting up your system
  • 19. Setting up your system
  • 20. Making changes to your local repo
  • 21. Committing changes to your local repo
  • 22. Publishing/Pushing changes to GitHub
  • 23. Files pushed to GitHub
  • 24. Publish & Sync Vs. Push & Pull
  • 25. General Collaborative Development • Shared single repository with access permissions • You can push and pull
  • 26. Collaborative Development in Public repos/Open Source projects -Fork & Pull Requests Overview- Your version of Main Repo’s files created (Your Fork) Main Repo (Source Repo) Fork Review Pull Requests & Merge 1 2 4 Make Changes (Add/modify files) & commit changes You Send Pull Request (Goes to Main Repo admin) 3 Main Repo Admin You You
  • 27. Collaborative Development in Public repos/Open Source projects • Fork – Makes your own repo called a fork – Freedom to change – Isolated • Push(in this context) – You push your changes to your repo(your fork) • Pull Request – You send pull request to main repo admin – Main Repo admin reviews the code changes and accepts & merges your pull request
  • 28. Misc. GitHub Stuff • Your email is associated with your commits • Can hide email for privacy
  • 29. Thank You Please provide feedback on http://bit.ly/githubsession Accompanying text article at : http://c-smil.es/githubarticle blog: @ashoka_rkt codeSmiles.com