diff --git a/html_output/index.html b/html_output/index.html index f9d061f..3088724 100644 --- a/html_output/index.html +++ b/html_output/index.html @@ -9,7 +9,7 @@ then do a little branch-based website exercise published live.

Archiving analogy:

What Git is not

Ecosystem

Archiving analogy:

What Git is not

Ecosystem

Typical workflow

Workshop outcome

Each participant will:

Install Git

Check first:

git --version

If missing:

Minimum requirement: you can run git in a terminal.

Core concept: three areas

  1. Working tree: your files right now
  2. Staging area (index): selection for the next deposit
  3. Repository history: commits (deposits)

This is why Git feels "archival":

Commands: the essential set

Command: git init

Create a repository in the current folder. Use this when you are creating and working on your own projects.

git init

Creates a .git/ directory containing history + metadata.

For the exercise we will use git clone instead of git init.

Command: git clone

Cloen (copy) a repository in the current folder.

git clone https://git.hackersanddesigners.nl/hrk/braids <destination>

Downloads a repo from the web, complete with the full commit history and all changes.

Command: git status (your dashboard)

git status

Shows:

Command: git add (select files)

Stage files for the next commit.

git add index.html
diff --git a/slides.rst b/slides.rst
index f1c20cc..0c8c3c1 100644
--- a/slides.rst
+++ b/slides.rst
@@ -53,6 +53,7 @@ Archiving analogy:
 What Git is not
 ===============
 
+- Git ≠ Github!
 - Not a backup system (though it can help)
 - Not a file sync tool
 - Not a CMS