Differences

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

--- git [2026/07/08 22:14] – [checkout] jhagstrand
+++ git [2026/08/06 07:54] (current) – [repository] jhagstrand
@@ Line 52: / Line 52: @@
 === bare===
 a bare repository is a folder named project.git\\
-a non-bare repository is a subfolder named .git, co-residing in the project folder along with the working copy\\
+a non-bare repository is a sub-folder named .git, co-residing in the project folder along with the working copy\\
-  git init
+  git init  # executed from within a new project folder, creates the .git folder
-  git clone
+  git init --bare flash.git  # create a new sub-folder named flash.git
+  git clone <server.path>.flash.git # create sub-folder named flash, within which lies the .git sub-folder
 ====remote====
@@ Line 273: / Line 275: @@
 This allows developers to work on multiple ideas at once, and switch back and forth.
-=== git checkout <file> ===
+**git checkout <file>**
 When you change your mind about the changes you've made, restore the file back to where it was before you started.
-=== git checkout <commit> ===
+**git checkout <commit>**
 When I'm testing my app and I'm not sure if my latest commit was successful,
 I can temporarily switch back to the previous commit and test that to refresh my memory.
@@ Line 285: / Line 286: @@
 Anytime the HEAD is pointed at a commit other than the one at the top of the current branch, it is considered detached.
 Repeat the git checkout <branch> to implicitly reattach the HEAD.
+==== checkout ====
+The repo is a library of commits.
+At any time, you can checkout a whole commit or a specific file within that commit.
+A branch is a pointer to a commit.
+The HEAD is also a pointer to a commit.
+When the HEAD points to a commit that is not also the top of a branch, the HEAD is considered "detached".
+The checkout command does two things:
+. Points the HEAD to the specified commit.
+. Brings the working tree into line with the new HEAD commit.
+You can specify a commit, a branch, or a file.
+  git checkout <branch>
+  git checkout <commit>
+  git checkout <file>
+You can specify a branch or a commit; either way you are specifying a commit.
+If you specify a file, there is no need to move the HEAD.  It just modifies that one file in the working tree to bring it into line with the current commit.
+Younger developers who don't yet fully understand the checkout command, in 2019, introduced two new aliases.
+^ correct                ^ alias               ^
+| git checkout <branch>  | git switch <branch>  |
+| git checkout <file>    | git restore <file>   |
 ====diff====
@@ Line 296: / Line 331: @@
 By default diff compares all of the currently modified files.
-  git diff         # before the add
+  git diff           # before staging
-  git add .
+  git add .          # staging
-  git diff HEAD    # after the add
+  git diff HEAD      # after staging
+  git diff --staged  # after staging
 Additional options.
@@ Line 350: / Line 386: @@
 https://www.sitepoint.com/git-interactive-rebase-guide/
+==== Combinations ====
+Some git command options effectively execute multiple git commands simultaneously.
+Here are some examples.
+. git add .
+. git commit -m 'latest fix'
++2. git -a commit -m 'latest fix'      # combine add and commit
+. git clone <project>
+. git submodule init
+. git submodule update
++3. git submodule update --init
++2+3. git clone --recursive-submodules <project>
+. git fetch     # download patch files
+. git merge     # apply patches to local files
++2. git pull    # fetch and merge
+====Fork====
+In github ui, fork repo from voyc to hagstrand.  A fork is a server-side clone.
+Locally:
+	git clone xttps://github.com/hagstrand/flash flashbang   # specified target <directory>
+	git remote add upstream xttps:github.com/voyc/flash   # second remote
+	git pull --rebase upstream master   # pull changes from upstream, update local, no commit
+	# pull does a fetch and merge into local directory.  No need to commit.
+	git push origin master
+	Todo: Rename?
+	Todo: In github UI, “Pull Request” to bring forked project back into upstream.
 ===== How to use =====
@@ Line 631: / Line 700: @@
 	git submodule update --init   # copies entries from .gitmodules to .git/config, and pulls each
-==== Combinations ====
-Some git command options effectively execute multiple git commands simultaneously.
-Here are some examples.
-. git add .
-. git commit -m 'latest fix'
-+2. git -a commit -m 'latest fix'      # combine add and commit
-. git clone <project>
-. git submodule init
-. git submodule update
-+3. git submodule update --init
-+2+3. git clone --recursive-submodules <project>
-. git fetch     # download patch files
-. git merge     # apply patches to local files
-+2. git pull    # fetch and merge
-====Fork====
-In github ui, fork repo from voyc to hagstrand.  A fork is a server-side clone.
-Locally:
-	git clone xttps://github.com/hagstrand/flash flashbang   # specified target <directory>
-	git remote add upstream xttps:github.com/voyc/flash   # second remote
-	git pull --rebase upstream master   # pull changes from upstream, update local, no commit
-	# pull does a fetch and merge into local directory.  No need to commit.
-	git push origin master
-	Todo: Rename?
-	Todo: In github UI, “Pull Request” to bring forked project back into upstream.
-====See the current changes====
-	git diff  # before staging (git add *)
-	git diff --staged # after staging
 ==== Remove a submodule ====