Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:git [2023/11/20 09:24] – [Track Changes] willtools:git [2026/06/17 14:17] (current) – [Git] will
Line 4: Line 4:
 Alternative SCM tools include ''[[https://fossil-scm.org/|fossil]]'', ''[[https://www.mercurial-scm.org/|hg]]'', ''[[https://pijul.org/|pijul]]''. For version controlling (large binary/non-text neuroimaging) data, see [[https://handbook.datalad.org/|datalad]] or [[https://dvc.org/|dvc]] Alternative SCM tools include ''[[https://fossil-scm.org/|fossil]]'', ''[[https://www.mercurial-scm.org/|hg]]'', ''[[https://pijul.org/|pijul]]''. For version controlling (large binary/non-text neuroimaging) data, see [[https://handbook.datalad.org/|datalad]] or [[https://dvc.org/|dvc]]
  
-''git'' is not github. [[https://github.com|Github]] is a Microsoft-owned source forge adding a social network, identity services, and other features not included in the git system (issue tracking, patch/fork management). Other forges include [[https://gitlab.com|gitlab]], [[https://sr.ht/|sr.ht]], [[https://codeberg.org/|codeberg]].+''git'' is not github. [[https://github.com|Github]] is a Microsoft-owned source forge adding a social network, identity services, and other features not included in the git system (issue tracking, patch/fork management). Other forges include [[https://gitlab.com|gitlab]], [[https://sr.ht/|sr.ht]], [[https://codeberg.org/|codeberg]], [[https://radicle.dev/|radicle]].  
 + 
 +See [[:tools:github]] for integrating local repos with github remote.
  
  
Line 12: Line 14:
   * https://git-scm.com/doc   * https://git-scm.com/doc
  
-===== Using ===== +===== Track Changes ===== 
-==== Track Changes ====+ 
 +{{:tools:pasted:20250918-141941.png?300}} 
 + 
 +On the command line in terminal/with shell, using git follows the ''add'',''commit'',''push'' pattern.  
 +Need a mnemonic? Think of the ''**A**dorable **C**omputer **P**enguins'' on the [[:tools:mobaxterm]] screensaver.
  
-On the command line in terminal/with shell, using git follows the ''add'',''commit'',''push'' pattern:  
 <code> <code>
 git add $file   # move changes in $file to "staging" git add $file   # move changes in $file to "staging"
Line 21: Line 26:
 git push        # send changes to a server (e.g. github) git push        # send changes to a server (e.g. github)
 </code> </code>
 +
 +<WRAP alert round>
 + **Don't give file paths to ''commit'' or ''push''**.
 +
 +Only the ''git add'' (or friends like ''git mv'' and ''git rm'') command takes file paths as arguments.
 +
 +''git commit'' and ''push'' work on the cumulative ''add''s to create a single snapshot, not individual files.
 +</WRAP>
  
 By default, ''git commit'' will open [[:tools:vim]] to use to write the commit message.  By default, ''git commit'' will open [[:tools:vim]] to use to write the commit message. 
Line 29: Line 42:
   - '':wq'' to write and quit.   - '':wq'' to write and quit.
  
-=== Commit messages ===+==== Commit messages ====
  
 Each commit in git includes a human-annotated short description in prose. While it's tempting and easy use `"update"` as the entire commit message, future you and colleges will appreciate a more detailed history. There are competing specifications to help guide better commit messages: Each commit in git includes a human-annotated short description in prose. While it's tempting and easy use `"update"` as the entire commit message, future you and colleges will appreciate a more detailed history. There are competing specifications to help guide better commit messages:
Line 35: Line 48:
   * https://gitmoji.dev/specification   * https://gitmoji.dev/specification
  
-== Examples ==+=== Examples ===
 Two commit messages in ''conventional commits'' vs ''gitmoji'' Two commit messages in ''conventional commits'' vs ''gitmoji''
 <code> <code>
Line 47: Line 60:
 </code> </code>
  
-==== See Changes ====+===== See Changes ===== 
 A huge benefit of version control is to see the what's changed. This can be done with web, graphical, and command line interfaces. A huge benefit of version control is to see the what's changed. This can be done with web, graphical, and command line interfaces.
  
Line 63: Line 77:
   * push ''/'' to start a search   * push ''/'' to start a search
   * push ''q'' to quit   * push ''q'' to quit
-==== Github https push ==== 
-To push to ''https'' (vs ssh like ''git@'') repos, you'll need to use a personal authentication token when prompted for a password. See [[https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens|github's documentation]] 
-  
-==== ssh push ==== 
-''git push'' can use ssh authentication. You need a key likely in ''~/.ssh/id_rsa.pub''.  
- 
- 
-Contents of ''~/.ssh/id_rsa.pub'' should be pasted into ''new ssh key'' modal on https://github.com/settings/keys ((''top right user icon''->''settings''->''ssh and GPG keys'' -> ''new ssh key'')) 
-{{:tools:pasted:20231024-130110.png}} 
- 
- 
-If ''~/.ssh/id_rsa.pub'' doesn't exist, ''ssh-keygen'' can make it (use empty password for convience. hit enter at password prompt to leave blank). See more [[https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent|documentaiton on github]] 
  
-==== Advanced ====+===== Advanced =====
   * [[https://git-scm.com/docs/git-worktree|working trees]] for working on more than one branch at a time   * [[https://git-scm.com/docs/git-worktree|working trees]] for working on more than one branch at a time
   * ''git add $file; git commit --amend --noedit; git push --force''   * ''git add $file; git commit --amend --noedit; git push --force''
   * rebase, esp with [[https://magit.vc/manual/magit/Rebasing.html|emacs+magit's rebase UI]]    * rebase, esp with [[https://magit.vc/manual/magit/Rebasing.html|emacs+magit's rebase UI]] 
-  * [[https://jvns.ca/blog/2023/11/01/confusing-git-terminology/|confusing terms]]b+  * [[https://jvns.ca/blog/2023/11/01/confusing-git-terminology/|confusing terms]] 
 +  * [[https://jvns.ca/blog/2024/02/16/popular-git-config-options/|popular git config options]]