[HOLD] Version Control for Everyone
Introduction
- Version control: It’s not just for programmers
- Tech writing
- What you should know
- No specific experience required!
- You have digital projects
- You want to “fail better”
- You might not have all software
- Using the exercise files
Introducing Version Control
Our menifesto: Everyone makes mistakes
- Some misconception
- It’s only for programmer
- It’s a lot of extra work
- The software is hard to use I’d have to use the command line
- I work alone, so there’s no need
Our software and why we need it
- What we’re using and wy
- Git is popular, free and good
- git is distributed
- Backups are still very critical!
- Version control is for (mostly) work
- Some other examples
- Mac has version of data on the files
- WordPress had post revisions
- Good Docs has version histories
- Dropbox version of files in last 30 days
How to get started
Introducing the essential terminology
- Text vs Binary files
- Version control loves text
- Repository
- The folder
- Commit
- A unit of work
- Checkout/Clone
- Getting a copy
- Branch
- Where experiments happen
- Merge
- Bring a branch back home
- Tag
- Label for a point to time
Installing a visual Git app
- Sublime merge
- Gitkraken you have account
- Github desktop have pre-built binaries
How to start tracking a project
Doing a piece of work