|
1 | | ---- |
2 | | -sidebar_position: 10 |
3 | | ---- |
4 | | - |
5 | | -# Index |
6 | | - |
7 | | -Index of terminology within this tutorial |
8 | | - |
9 | | -### Push |
10 | | ->*noun, verb*: To publish your changes to a repository: `git push` |
11 | | -
|
12 | | -### Pull |
13 | | ->*noun, verb*: To fetch and integrate changes in a remote [repository](#repository-repo) with the changes in a local [repository](#repository-repo). `git pull`*` remote-name branch-name`* |
14 | | -
|
15 | | -### Repository (*repo*) |
16 | | ->*noun*: A type of centrally located storage where you can keep all your project's files and resources. |
17 | | -
|
18 | | -### Clone |
19 | | ->*verb*: To create a copy of a specific repository or branch within a repository: `git clone` |
20 | | -
|
21 | | -### Merge |
22 | | ->*verb*: To combine a forked history back together again: `git merge` |
23 | | -
|
24 | | -### Merge Conflict |
25 | | -> *noun*: An issue where performing a merge causes issues in git being able to auto-resolve edit differences of two commits. Specifically, it occurs when two branches modify teh same region of a file. Common ways to handle the error are either to manually edits the file or to use `git mergetool`. |
26 | | -
|
27 | | -### Commit |
28 | | ->*noun, verb*: A "revision" or an individual change to a file (or a set of files). Commits usually contain a message which is a brief description of what changes were made. Useful [diagram](../../../../static/img/git-tutorial/git-workflow-2.png). `git commit` |
29 | | -
|
30 | | -### `mkdir` |
31 | | ->*command*: The command to create a new directory in the CLI. Make directory. |
32 | | -
|
33 | | -### `cd` |
34 | | ->*command*: The command to change the current working directory in the CLI. Change directory. |
35 | | -
|
36 | | -### `ls` |
37 | | ->*command*: The command to view the content of the current working directory in the CLI. List. |
38 | | -
|
39 | | -### Visual Studio Code |
40 | | ->*Source-Code Editor*: <br/> A free and open-source source-code editor developed by Microsoft for Windows, Linux, macOS, and various web browsers. It has capabilities to help debug code, perform syntax highlighting, inteligent code completion, snippits, code refactoring, and embedded version control with Git. It also offers the ability to change themes, add keyboard shortcuts, and add functionality with extensions. |
41 | | -
|
42 | | -### Vim |
43 | | ->*Text Editor* <br /> A free and open-source, screen-based text editor. It is an improved version of the **vi** editor. It's primary interface is in text user interface with commands rather than menus or icons. |
44 | | -
|
45 | | -### Stage |
46 | | ->*verb*: To prepare a file for a [commit](#commit) by placing it into the [staging area](#staging-area). `git stage` |
47 | | -
|
48 | | -### Staging area |
49 | | ->*noun*: The *conceptual* area between your working directory and your repostory that maintains all of your [staged](#stage) changes. A useful [diagram](../../../../static/img/git-tutorial/staging-area.png). |
50 | | -
|
51 | | -### `git status short` |
52 | | -> git status --short status flags are |
53 | | -> * ?? $\rightarrow$ Untracked changes |
54 | | -> * A $\rightarrow$ Files added to be staging area |
55 | | -> * M $\rightarrow$ Modified Files |
56 | | -> * D $\rightarrow$ Deleted Files |
57 | | -
|
58 | | -### Branch |
59 | | -> *noun*: A new/seperate version of the main [repository](#repository-repo). |
60 | | -
|
61 | | -### Checkout |
62 | | -> *verb*: To move from a branch to another one. `git branch `*`branch_name`*. |
63 | | -
|
| 1 | +--- |
| 2 | +sidebar_position: 10 |
| 3 | +--- |
| 4 | + |
| 5 | +# Index |
| 6 | + |
| 7 | +Index of terminology within this tutorial |
| 8 | + |
| 9 | +### Push |
| 10 | +>*noun, verb*: To publish your changes to a repository: `git push` |
| 11 | +
|
| 12 | +### Pull |
| 13 | +>*noun, verb*: To fetch and integrate changes in a remote [repository](#repository-repo) with the changes in a local [repository](#repository-repo). `git pull`*` remote-name branch-name`* |
| 14 | +
|
| 15 | +### Repository (*repo*) |
| 16 | +>*noun*: A type of centrally located storage where you can keep all your project's files and resources. |
| 17 | +
|
| 18 | +### Clone |
| 19 | +>*verb*: To create a copy of a specific repository or branch within a repository: `git clone` |
| 20 | +
|
| 21 | +### Merge |
| 22 | +>*verb*: To combine a forked history back together again: `git merge` |
| 23 | +
|
| 24 | +### Merge Conflict |
| 25 | +> *noun*: An issue where performing a merge causes issues in git being able to auto-resolve edit differences of two commits. Specifically, it occurs when two branches modify teh same region of a file. Common ways to handle the error are either to manually edits the file or to use `git mergetool`. |
| 26 | +
|
| 27 | +### Commit |
| 28 | +>*noun, verb*: A "revision" or an individual change to a file (or a set of files). Commits usually contain a message which is a brief description of what changes were made. Useful [diagram](../../../../static/img/git-tutorial/git-workflow-2.png). `git commit` |
| 29 | +
|
| 30 | +### `mkdir` |
| 31 | +>*command*: The command to create a new directory in the CLI. Make directory. |
| 32 | +
|
| 33 | +### `cd` |
| 34 | +>*command*: The command to change the current working directory in the CLI. Change directory. |
| 35 | +
|
| 36 | +### `ls` |
| 37 | +>*command*: The command to view the content of the current working directory in the CLI. List. |
| 38 | +
|
| 39 | +### Visual Studio Code |
| 40 | +>*Source-Code Editor*: <br/> A free and open-source source-code editor developed by Microsoft for Windows, Linux, macOS, and various web browsers. It has capabilities to help debug code, perform syntax highlighting, inteligent code completion, snippits, code refactoring, and embedded version control with Git. It also offers the ability to change themes, add keyboard shortcuts, and add functionality with extensions. |
| 41 | +
|
| 42 | +### Vim |
| 43 | +>*Text Editor* <br /> A free and open-source, screen-based text editor. It is an improved version of the **vi** editor. It's primary interface is in text user interface with commands rather than menus or icons. |
| 44 | +
|
| 45 | +### Stage |
| 46 | +>*verb*: To prepare a file for a [commit](#commit) by placing it into the [staging area](#staging-area). `git stage` |
| 47 | +
|
| 48 | +### Staging area |
| 49 | +>*noun*: The *conceptual* area between your working directory and your repostory that maintains all of your [staged](#stage) changes. A useful [diagram](../../../../static/img/git-tutorial/staging-area.png). |
| 50 | +
|
| 51 | +### `git status short` |
| 52 | +> git status --short status flags are |
| 53 | +> * ?? $\rightarrow$ Untracked changes |
| 54 | +> * A $\rightarrow$ Files added to be staging area |
| 55 | +> * M $\rightarrow$ Modified Files |
| 56 | +> * D $\rightarrow$ Deleted Files |
| 57 | +
|
| 58 | +### Branch |
| 59 | +> *noun*: A new/seperate version of the main [repository](#repository-repo). |
| 60 | +
|
| 61 | +### Checkout |
| 62 | +> *verb*: To move from a branch to another one. `git branch `*`branch_name`*. |
| 63 | +
|
0 commit comments