# Git Workflow for Small Projects

Use Git to inspect changes, commit one idea at a time, tag releases, and keep rollback possible.

## Outcome
Make a small project safer to edit, deploy, and roll back.

## Safe first step
git status shows what changed before you commit or deploy.

## Ladder steps
### 1. Check status first
Know whether the tree is clean, dirty, or untracked.

Check: git status names changed files.

### 2. Review the diff
Inspect what changed before staging it.

Check: git diff shows the exact lines.

### 3. Commit one idea
Small commits make rollback and review easier.

Check: The commit message names the purpose.

### 4. Tag a release
A tag can mark the deployed version.

Check: git tag identifies a stable point.

## Examples
### Show changed files compactly
```sh
git status --short
```
Expected signal: A two-column status list

### Review one file diff
```sh
git diff -- path/to/file
```
Expected signal: Added and removed lines

### Check recent commits
```sh
git log --oneline -5
```
Expected signal: Recent commit hashes and messages

## Common traps
- Deploying without checking the diff.
- Mixing unrelated changes in one commit.
- Using Git as a backup only after something breaks.

## Practice task
Change one line in a sample file, inspect it with git diff, stage it, and write a commit message that describes only that change.

## Next steps
- Use release folders.
- Write deploy notes.
- Pair Git with static hosting checks.

## Related
- [Git status short command](https://linuxoneliners.com/commands/git-status-short/)