Looking familiar?
(Healy 2019)
Trunk:
Unnamed branch of a file tree under revision control
(Commons 2009)
Structure:
The structure of the revisions is not a tree (although it is often referred to as the revision tree) but a directed acyclic graph.
(Commons 2009)
Tag:
A tag assigns a label to a revision (including many files) allowing to directly jump to that revision. Often used to label a specific version of a software.
(Commons 2009)
Let’s check git out!
https://github.com/TwlyY29/dmkg_intro_to_git
https://github.com/TwlyY29/dmkg_intro_to_git
Let’s git going!
Useful resources:
https://git-scm.com/book/en/v2 (Chacon and Straub 2014)
Useful resources: https://git-scm.com/book/en/v2 (Chacon and Straub 2014)
And please have a look at the next slide!
Avoiding vim
-hell for git commit
s:
Change the default text editor for commit messages in the
git bash
before you do anything else:
Windows users:
git config --global core.editor "notepad"
Mac users:
git config --global core.editor “open -e -W -n”
https://zxtech.wordpress.com/2020/03/29/setting-textedit-as-default-git-editor/
Branching:
Duplication of an object under version control. Objects can then be modified separately and in parallel so that they become different. These objects are called branches.
(Commons 2009)
Merge:
A fundamental operation that reconciles multiple changes made to a version- controlled collection of files. Necessary when files are modified on two independent branches. The result is a single collection of files that contains both sets of changes.
(Commons 2009)
Useful resources: https://git-scm.com/book/en/v2 (Chacon and Straub 2014)
Meld for Linux: sudo apt install meld
Useful resources: https://git-scm.com/book/en/v2 (Chacon and Straub 2014)
Git is great for collaboration. For example:
Merge/Pull requests:
Useful resources: docs.github.com > Collaborative Coding > Pull Requests > Overview
What is the most central requirement to efficiently use git?
Use Plain Text Files.
LZV.NRW (2023)