Difference between revisions of "Git"
(Reformat for more learning perspective) |
|||
Line 1: | Line 1: | ||
− | '''Git''' is a distributed | + | '''Git''' is a distributed version control system (VCS), designed to work well with highly non-linear workflows. It was initially conceived to support development of the Linux kernel, and has since become the most widely-used VCS for software development. |
Git is used to maintain most of the software used by the group, including [[PHASTA]], [[Chef]], [[VTKpytools|vtkpytools]], and more. Learning git will allow you to make changes to these codes and share them with the group, in addition to allowing you to test proof-of-concept codes without fear of accidentally deleting code. | Git is used to maintain most of the software used by the group, including [[PHASTA]], [[Chef]], [[VTKpytools|vtkpytools]], and more. Learning git will allow you to make changes to these codes and share them with the group, in addition to allowing you to test proof-of-concept codes without fear of accidentally deleting code. | ||
Line 6: | Line 6: | ||
== Learning Git == | == Learning Git == | ||
− | If you're | + | If you're not familiar with version control systems, see the [https://git-scm.com/video/what-is-version-control What is Version Control?] video for some motivation on why VCS is used. |
− | === Basic Git | + | Next, if you're completely new to <code>git</code, the [https://git-scm.com/video/what-is-git What is git?] video from the maintainers of <code>git</code> is a great primer. |
+ | |||
+ | Once you've gotten a general idea on VCS and the core concepts of git, try out [https://learngitbranching.js.org/ Learn Git Branching]. It is a great interactive, visual training program that shows the basics. It'll help you learn the actual command line functions of git while the visuals help to give an understanding of what ''exactly'' those commands do. Even if you're not completely new to git, it may help you to understand some concepts you didn't before. | ||
+ | |||
+ | === Refreshers === | ||
+ | |||
+ | If you need a quick refresher on how to do certain actions, or just a quick cheat sheet [https://ndpsoftware.com/git-cheatsheet.html#loc=stash; this interactive cheatsheet] is quite nice for figuring out what commands you need to move changes from one "stage" to another. | ||
+ | |||
+ | == Basic Git == | ||
Basic information to get started with Git can be found at http://rogerdudler.github.io/git-guide/. | Basic information to get started with Git can be found at http://rogerdudler.github.io/git-guide/. | ||
− | + | ===Git repository (repo)=== | |
: Is a directory that contains files of the current branch and a hidden <code>.git</code> directory | : Is a directory that contains files of the current branch and a hidden <code>.git</code> directory | ||
: Contains an '''Index''' in <code>.git</code> that acts as a staging area for all your branches | : Contains an '''Index''' in <code>.git</code> that acts as a staging area for all your branches | ||
Line 18: | Line 26: | ||
: Your PHASTA repository should always be at <code>~/git-phasta/phasta</code> | : Your PHASTA repository should always be at <code>~/git-phasta/phasta</code> | ||
− | + | ===Create a new repository=== | |
: <code>git init</code> | : <code>git init</code> | ||
− | + | ===Checkout a repository=== | |
: <code>git clone /path/to/repo</code> | : <code>git clone /path/to/repo</code> | ||
: <code>git clone user@host:/path/to/repo</code> | : <code>git clone user@host:/path/to/repo</code> | ||
− | + | ===Add files to be tracked in the git index=== | |
: <code>git add <filename1> <filename2> ...</code> | : <code>git add <filename1> <filename2> ...</code> | ||
: <code>git add *</code> | : <code>git add *</code> | ||
: <code>git add -u</code> (all files updated since last commit) | : <code>git add -u</code> (all files updated since last commit) | ||
− | + | ===Commit changes to HEAD=== | |
: <code>git commit -m "my_username: my comments about this commit"</code> | : <code>git commit -m "my_username: my comments about this commit"</code> | ||
− | + | ===Push changes to remote repo=== | |
: <code>git push origin master</code> (pushes the <code>master</code> branch to the original/main repo) | : <code>git push origin master</code> (pushes the <code>master</code> branch to the original/main repo) | ||
− | + | ===Connect to a remote server=== | |
: <code>git remote add origin <server></code> (connects <code><server></code> to your main, or <code>origin</code> repository) | : <code>git remote add origin <server></code> (connects <code><server></code> to your main, or <code>origin</code> repository) | ||
: <code>git remote add myrepo <server></code> (connects <code><server></code> to a named branch called <code>mybranch</code>) | : <code>git remote add myrepo <server></code> (connects <code><server></code> to a named branch called <code>mybranch</code>) | ||
: Note: <code><server></code> could be <code>user@host:/path/to/repo</code> | : Note: <code><server></code> could be <code>user@host:/path/to/repo</code> | ||
− | + | ===Create and delete branch=== | |
: <code>git checkout -b branch_name</code> (creates and checkout branch) | : <code>git checkout -b branch_name</code> (creates and checkout branch) | ||
: <code>git checkout master</code> (checkout master branch) | : <code>git checkout master</code> (checkout master branch) | ||
: <code>git branch -d branch_name</code> (delete branch we just created) | : <code>git branch -d branch_name</code> (delete branch we just created) | ||
− | + | ===Push branch to a remote=== | |
: <code>git push origin branch</code> (pushes from your main <code>origin</code> repo) | : <code>git push origin branch</code> (pushes from your main <code>origin</code> repo) | ||
− | + | ===Update and merge=== | |
: <code>git pull</code> (so all branches are up-to-date for the merge) | : <code>git pull</code> (so all branches are up-to-date for the merge) | ||
: <code>git merge origin/master</code> (merges current branch with <code>origin</code>'s <code>master</code> branch) | : <code>git merge origin/master</code> (merges current branch with <code>origin</code>'s <code>master</code> branch) | ||
: If a merge has conflicts, you need to edit the conflict files provided by Git, and then mark them as merged with <code>git add</code> | : If a merge has conflicts, you need to edit the conflict files provided by Git, and then mark them as merged with <code>git add</code> | ||
− | + | ===Compare code in different branches=== | |
: <code>git diff <branch_a> <branch_b></code> | : <code>git diff <branch_a> <branch_b></code> | ||
− | + | ===View history of commits=== | |
: <code>git log</code> | : <code>git log</code> | ||
: <code>git log --author=foo</code> | : <code>git log --author=foo</code> | ||
Line 64: | Line 72: | ||
: <code>git log --name-status</code> (show which files changed in each commit) | : <code>git log --name-status</code> (show which files changed in each commit) | ||
: <code>git log --help</code> (more information) | : <code>git log --help</code> (more information) | ||
− | |||
== Git Prompt Statement (PS1) == | == Git Prompt Statement (PS1) == |
Revision as of 08:29, 5 September 2020
Git is a distributed version control system (VCS), designed to work well with highly non-linear workflows. It was initially conceived to support development of the Linux kernel, and has since become the most widely-used VCS for software development.
Git is used to maintain most of the software used by the group, including PHASTA, Chef, vtkpytools, and more. Learning git will allow you to make changes to these codes and share them with the group, in addition to allowing you to test proof-of-concept codes without fear of accidentally deleting code.
Contents
- 1 Learning Git
- 2 Basic Git
- 2.1 Git repository (repo)
- 2.2 Create a new repository
- 2.3 Checkout a repository
- 2.4 Add files to be tracked in the git index
- 2.5 Commit changes to HEAD
- 2.6 Push changes to remote repo
- 2.7 Connect to a remote server
- 2.8 Create and delete branch
- 2.9 Push branch to a remote
- 2.10 Update and merge
- 2.11 Compare code in different branches
- 2.12 View history of commits
- 3 Git Prompt Statement (PS1)
Learning Git
If you're not familiar with version control systems, see the What is Version Control? video for some motivation on why VCS is used.
Next, if you're completely new to git</code, the What is git? video from the maintainers of <code>git
is a great primer.
Once you've gotten a general idea on VCS and the core concepts of git, try out Learn Git Branching. It is a great interactive, visual training program that shows the basics. It'll help you learn the actual command line functions of git while the visuals help to give an understanding of what exactly those commands do. Even if you're not completely new to git, it may help you to understand some concepts you didn't before.
Refreshers
If you need a quick refresher on how to do certain actions, or just a quick cheat sheet this interactive cheatsheet is quite nice for figuring out what commands you need to move changes from one "stage" to another.
Basic Git
Basic information to get started with Git can be found at http://rogerdudler.github.io/git-guide/.
Git repository (repo)
- Is a directory that contains files of the current branch and a hidden
.git
directory - Contains an Index in
.git
that acts as a staging area for all your branches - Contains a HEAD in
.git
that points to the last commit you made - Your PHASTA repository should always be at
~/git-phasta/phasta
Create a new repository
-
git init
Checkout a repository
-
git clone /path/to/repo
-
git clone user@host:/path/to/repo
Add files to be tracked in the git index
-
git add <filename1> <filename2> ...
-
git add *
-
git add -u
(all files updated since last commit)
Commit changes to HEAD
-
git commit -m "my_username: my comments about this commit"
Push changes to remote repo
-
git push origin master
(pushes themaster
branch to the original/main repo)
Connect to a remote server
-
git remote add origin <server>
(connects<server>
to your main, ororigin
repository) -
git remote add myrepo <server>
(connects<server>
to a named branch calledmybranch
) - Note:
<server>
could beuser@host:/path/to/repo
Create and delete branch
-
git checkout -b branch_name
(creates and checkout branch) -
git checkout master
(checkout master branch) -
git branch -d branch_name
(delete branch we just created)
Push branch to a remote
-
git push origin branch
(pushes from your mainorigin
repo)
Update and merge
-
git pull
(so all branches are up-to-date for the merge) -
git merge origin/master
(merges current branch withorigin
'smaster
branch) - If a merge has conflicts, you need to edit the conflict files provided by Git, and then mark them as merged with
git add
Compare code in different branches
-
git diff <branch_a> <branch_b>
View history of commits
-
git log
-
git log --author=foo
-
git log --pretty=oneline
(show each commit as one line) -
git log --graph --oneline --decorate --all
(ASCII tree of branches, commits, merges) -
git log --name-status
(show which files changed in each commit) -
git log --help
(more information)
Git Prompt Statement (PS1)
- Acquire
git-prompt.sh
from https://github.com/git/git/blob/master/contrib/completion/git-prompt.sh, and save it somewhere like~/.git-prompt.sh
- Edit your
~/.bashrc
to saysource ~/.git-prompt.sh
before the lines that set yourPS1
- Modify your
PS1
string to include$(__git_ps1 "(%s)")
where you want the current branch to appear in your prompt