Basics of Github - Concepts

What is GitHub ? 

• Website and service that facilitates software development  by allowing people to store code in containers, repositories and tracking changes made to the code.
• Uses Git, a version-control development tool to manage projects by tracking changes to files and allow multiple people to work on the same project.
  • Github is a service, Git is a development tool that can be used by you of outside of and without github

 

Why is it important?

• Grants developers to the massive community of developers around the world who openly share codes , projects , and software development tools
• Git repository → project managed with Git 

GitHub = Tool for working with Git !!

Main == Master Branches 

 

Steps of How it works with pictures : 

---

Managing Branches 

Isolate other people’s codes (works) to avoid conflict. Git ables teammates to create their own branches off of the main project (bug-fixes, new features, experimental code, ect) 

• Branch = divergence from the main project 
  • Branching out make a new state of current code, which you can work without affecting the important main state the code
  • Can create as many branches  and create branches off of other branches
  • Using separate branches keep the main project intact and unaffected before the changes are reviewed and merged
  • Main branch = the one where all changes eventually get merged back into (main) → usually the working version of a project and contains the production code MERGE CLEAN AND CORRECT CODE !
  • A new branch should be created when adding new feature , bug fixes or experiments with a relevant name

Commit along with a message describing work, and push commit to remote Github repository

---

Creating a Pull Request 

Pull requests = allow collaborators to review and give feedback on proposed code changes before they are merged to the main branch 

• Include as much relevant detail in description to save review time

• Don't only comment on what should be changed, but why it should be changed. 
• Be as clear as possible with comments and make sure to be clear as to what to modify
• Try to spot potential errors 

Pull request → other members can review it up on Github. Include description , which github will display all the files with the changes created“+” button = add comment regarding line