---
# System prepended metadata

title: Git-intro update

---

# Git-intro update
This is the outline for the git-intro lesson rework.  Start specifically and expand

```
## Lesson page
* page section
** point within a section
```
# (day 1)
## Motivation
(mostly same as before, but move to google docs example)
## Your first project
* Our recipe book
  - README.md
  - LICENSE
  - recipes/
    - few existing recipees
  - gitignore?
    - GH lets me upload files anyway without warning 
  - (private and public copy)
  - added day 3: action to verify
    - check markdown
    - or check for certain ingredient 
  - added day 3: pages deploy
* Make a copy to work on (fork repository)
* Exercise 1a: Fork (20 min)
  * Do the fork
  * This i
## Archaeology part 1
* Exercise 1b: Archeology
  * Explore a few things (copy from "inspecting history")
    * "grep" (which foods include a certain ingredient)
    * annotate (who has contributed to this recipe)
      * at which commit did an ingredient get introduced or modified? 
    * Contributors page (Who all has contributed?)
    * How old is each recipe, and how many changes? (look at history)
    * When was each recipe last modified? (file browser)
    * Can you use these recipes yourself? (license)
    * Browse issues and pull requests, any idea what that might be good for?
    * Browse commit history: are commit messages understandable?
  * Preparation:
    * RB creates starting repo
    * we need a group of staff preparing this
    * each adds one and maybe changes one recipe 
    * we need two versions: repo and repo-recorded

## Modify your copy (commit)
* 
* Exercise: commit
  * create a branch and commit to it
  * maybe also commit to main
  * browse network
  * compare branches
  * compare commits



## Merge branches and contribute to the project
* Exercise: Merge branches with PR
  * select from which to which
  * be careful about whether this is towards main on your copy or the repo where we forked from
  * browse network
  * optional: try also to send a PR towards the central repo (we merge few of those)
  
* Demo:
  * conflict
  * delete branches
  * create release (or optional exercise step)
* Discussion: Doing this locally.  We will start here tomorrow.
* Quiz:
  * how to find out which branches are safe to delete? 


# (day 2)

* What is Git, and what is a Git repository? (from git-intro)
* Configuring Git command line (from git-intro)
* Exercise: config/clone/commit/branch


## Archaeology part 2
(copy from archeology)
* Exercise: Arch part 2
* Exercise: push to clone / remote add push to default, OR init add commit remote add push 