An explanation of version control and tooling with git and GitHub
- Tracks the history of changes as people and teams collaborate on projects together.
- Keeps versions of your code. Ex: Saving a word document.
- Which changes were made?
- Who made the changes?
- When were the changes made?
- Why were changes needed?
gitis a distributed VCS.- Every developer's working copy of the code is also a repository that can contain the full history of all changes
gitproject. Directory with.gitfolder- The entire collection of files and folders associated with a project, along with each file’s revision history.
- The file history appears as snapshots in time called commits (like a picture), which are linked together and can be separated in branches
- Each commit log has who made the commit, when, what and why they were made. You provide why/what
- Rule of thumb: commit what you wouldn't want to lose.
- Commit message should be
- < 50 characters
- A present tense action verb (
Add/Update) followed by what was changed -
- A list of commits in a separate unit.
- 'Branching out'.
- Each branch should have a singular purpose.
- Usually for a feature or fix.
Note: Each command usually comes with their own options
- https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
- Add a
README.md(info about your repository for anyone to read) or any other file - Commit the file
- GitHub hosts repositories for you, so you and others can access them from anywhere.
- It's a collaborative platform
- Allows you to have docs/wiki, make issues (log features/bugs), pull requests and more
- Make a pull request to the repository below with your name and GitHub info in the
README.mdusing either GitHub or the command line - https://github.com/sirMerr/git-ppt
