remove overview

2022/2022-05-31_git-triology-part-1/slides/list.json

 [
     { "filename": "index.md" },
-    { "filename": "overview.md" },
     { "filename": "versioning.md" },
     { "filename": "what_is_git.md" },
     { "filename": "repository.md" },

2022/2022-05-31_git-triology-part-1/slides/overview.md

-# Overview
-
-Keep focus on real examples!
-
-Git
-Repository
-Github/Gitlab
-   - login
-   - find repo, report issue in the repo
-
-commit, history, visualization
-   - go the the file history and see what has changed in a last commit
-   - why so big separation of changes
-     - annotation, clear separation of changes on row level!
-
-branch
-visualization
-master/develop + feature branch
-   - look at the difference between branches
-   - clear separation
-
-fork - visualization
-- create fork
-- contribute using WebIDE (workflow - edit, commit)
-
-merge
-- propagate changes to other branches(forks) with REVIEW process!
-
-
-
-
-
-1. Basics (repository, branch, fork, merge, commit)
-   1. explanation of git version diagram (arrow is the change, node is a new stable state)
-   2. change ~ commit
-   3. explanation of branch (two parallel histories with a same ancestor)
-      1. master develop
-   4. fork (copy of of the whole repository with all branches)
-   5. independency why?
-      1. separation of changes by commit - compare with standard "versioning" of dropbox/onedrive/owncloud or labeling v1.2 manually 
-      2. separation of work into branches - compare with standard parallel work - making copy of file and renaming, then "putting it together"
-      3. separation of work into forks - copy of the whole directory to your local space (usually old versions are not preserved, no link to the previous folder ...)
-   6. Wrap-up - whole fork-branch-commit-merge
-2. Login
-3. Search for repo
-4. Report issue in a repo
-5. Fork
-6. Contribute using WebIDE (workflow - edit, commit)
-7. Merge request
-8. Review
-9. Wrap-up (glossary, complete workflow in git jargon and GitLab jargon)