TOC
| command line |
|---|
| - what is command line? commands they need to use with git: - export - open - cat - rm - cd - mv - pwd - mkdire - echo - touch - ls |
| Installing Git |
| introduction |
| - intro to VCS - intro to Git - what does git solves? working with team + saving versions - Git vs GitHub and other platforms |
| Git Basics |
| - Git repository concept - git init - git structure (.git folder) - Git Stages Concept - git status - git add - git configuration - git commit - .gitignore - markdown files |
| Git commit history |
| - git log - git show |
| Git clone |
| - introduction to github interface
- protocols HTTPS and SSH
- git clone
- git push
- git pull |
- Initialize a git repository in order to track changes.
- Create a new branch to isolate your changes.
- Place new or changed files into the staging area to prepare them for a commit.
- Remove files from the staging area before a commit.
- Commit new and changed files to a git repository.
Version control! As developers our code is our livelihood so it's important that we safely store our work... frequently. Not only that, we also want to track our changes as we make them. If we make a feature that ends up breaking the rest of our app we want to be able to go back to a point when our app was last working.
A staging step in git allows you to continue making changes to the working directory, and when you decide you wanna interact with version control, it allows you to record changes in small commits. ... Separating staging and committing, you get the chance to easily customize what goes into a commit.
