Skip to content

Commit 8842a70

Browse files
committed
feat (github): separating 'git background' from github module
1 parent 0eff999 commit 8842a70

2 files changed

Lines changed: 39 additions & 30 deletions

File tree

git-background.qmd

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: "Git Background"
3+
---
4+
5+
## Module Learning Objectives
6+
7+
By the end of this module, you will be able to:
8+
9+
- <u>Define</u> "version control"
10+
- <u>Describe</u> the difference between Git and GitHub
11+
12+
## Version Control Background
13+
14+
Version control systems (including Git) are built to preserve the iterative versions that we create on the way to a final product. For instance, when writing a scientific manuscript we might have several discrete stages (e.g., separate drafts after successive rounds of feedback from collaborators) as well as the sort of small-scale changes we don't necessarily preserve in separate files (e.g., workshopping a particular sentence for rhetorical flow).
15+
16+
**Version control systems provide a framework for preserving these changes without cluttering your computer with all of the files that precede the final version.**
17+
18+
<p align="center">
19+
<img src="images/comics/phd_comics_final.png" alt="Comic of a graduate student naming a file 'final.doc' then getting progressively more frustrated and making worse file names as that file received iterative comments from an advisor" width="60%"/>
20+
</p>
21+
22+
## Git-Specific Background
23+
24+
Git can be enabled on a specific folder/directory on your file system to version files within that directory (including sub-directories). In Git (and other version control systems) terms, this "tracked folder" is called a **repository** (which formally is a specific data structure storing versioning information).
25+
26+
Although there many ways to start a new repository, [GitHub](https://github.com/) (or any other cloud solutions, such as [GitLab](https://about.gitlab.com/)) provide among the most convenient way of starting a repository.
27+
28+
Let's distinguish between Git and GitHub:
29+
30+
- **Git**: version control software used to track files in a folder (a repository)
31+
- Git creates the versioned history of a repository
32+
- **GitHub**: website that allows users to store their Git repositories and share them with others (i.e. a graphical user interface or "GUI")
33+
34+
**GitHub is a company that hosts Git repositories online** and provides several collaboration features. GitHub fosters a great user community and has built a nice web interface to Git, also adding great visualization/rendering capacities of your data.
35+
36+
- **GitHub.com**: [github.com](https://github.com/)
37+
- **A user account**: [github.com/angelchen7](https://github.com/angelchen7)
38+
- **An organization account**: [github.com/lter](https://github.com/lter)

github.qmd

Lines changed: 1 addition & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,15 @@
11
---
2-
title: "Git & GitHub"
2+
title: "Using GitHub"
33
---
44

55
## Module Learning Objectives
66

77
By the end of this module, you will be able to:
88

9-
- <u>Describe</u> the difference between Git and GitHub
109
- <u>Navigate</u> GitHub via a web browser
1110
- <u>Use</u> GitHub to create a new repository
1211
- <u>Edit</u> a new repository through GitHub's interface
1312

14-
## Version Control Background
15-
16-
Version control systems (including Git) are built to preserve the iterative versions that we create on the way to a final product. For instance, when writing a scientific manuscript we might have several discrete stages (e.g., separate drafts after successive rounds of feedback from collaborators) as well as the sort of small-scale changes we don't necessarily preserve in separate files (e.g., workshopping a particular sentence for rhetorical flow).
17-
18-
**Version control systems provide a framework for preserving these changes without cluttering your computer with all of the files that precede the final version.**
19-
20-
<p align="center">
21-
<img src="images/comics/phd_comics_final.png" alt="Comic of a graduate student naming a file 'final.doc' then getting progressively more frustrated and making worse file names as that file received iterative comments from an advisor" width="60%"/>
22-
</p>
23-
24-
## Git-Specific Background
25-
26-
Git can be enabled on a specific folder/directory on your file system to version files within that directory (including sub-directories). In Git (and other version control systems) terms, this "tracked folder" is called a **repository** (which formally is a specific data structure storing versioning information).
27-
28-
Although there many ways to start a new repository, [GitHub](https://github.com/) (or any other cloud solutions, such as [GitLab](https://about.gitlab.com/)) provide among the most convenient way of starting a repository.
29-
30-
Let's distinguish between Git and GitHub:
31-
32-
- **Git**: version control software used to track files in a folder (a repository)
33-
- Git creates the versioned history of a repository
34-
- **GitHub**: website that allows users to store their Git repositories and share them with others (i.e. a graphical user interface or "GUI")
35-
36-
**GitHub is a company that hosts Git repositories online** and provides several collaboration features. GitHub fosters a great user community and has built a nice web interface to Git, also adding great visualization/rendering capacities of your data.
37-
38-
- **GitHub.com**: [github.com](https://github.com/)
39-
- **A user account**: [github.com/angelchen7](https://github.com/angelchen7)
40-
- **An organization account**: [github.com/lter](https://github.com/lter)
41-
4213
## Exploring GitHub
4314

4415
Let's navigate over to [GitHub](https://github.com/) and explore some of its features. Here is what the home screen looks like as of February 2022.

0 commit comments

Comments
 (0)