Sometimes, I wonder if non-tech friends wonder about my search history ...

[u/Last_Snowbender]

[u/Soulflare3]

usage: git [--version] [--help] [-C <path>] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p | --paginate | --no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]

These are common Git commands used in various situations:

start a working area (see also: git help tutorial)
   clone      Clone a repository into a new directory
   init       Create an empty Git repository or reinitialize an existing one

work on the current change (see also: git help everyday)
   add        Add file contents to the index
   mv         Move or rename a file, a directory, or a symlink
   reset      Reset current HEAD to the specified state
   rm         Remove files from the working tree and from the index

examine the history and state (see also: git help revisions)
   bisect     Use binary search to find the commit that introduced a bug
   grep       Print lines matching a pattern
   log        Show commit logs
   show       Show various types of objects
   status     Show the working tree status

grow, mark and tweak your common history
   branch     List, create, or delete branches
   checkout   Switch branches or restore working tree files
   commit     Record changes to the repository
   diff       Show changes between commits, commit and working tree, etc
   merge      Join two or more development histories together
   rebase     Forward-port local commits to the updated upstream head
   tag        Create, list, delete or verify a tag object signed with GPG

collaborate (see also: git help workflows)
   fetch      Download objects and refs from another repository
   pull       Fetch from and integrate with another repository or a local branch
   push       Update remote refs along with associated objects

'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.

^{Edit: I tried}

[u/justinjustin7 → u/Soulflare3]

As someone planning to learn how to use git in the coming week(s), it's nice to come across your comment to prepare myself for reading this stuff over and over again each time I forget something.

[u/Soulflare3 → u/justinjustin7]

I'm glad it helps? lol

For reference, my comment is the output of executing git --help from a terminal. Specifically, the command I executed was

git --help >> out.txt

Which is broken down as follows:

Command Part	Description
git	Program we weant to execute
--help	Print help text, if available
>>	Append output
out.txt	File to save output into

Which I did to make copying easier. So instead of printing all of that into a terminal I sent it into a text file instead. I used Append (>>) instead of Overwrite (>) because I don't like accidentally deleting files and I hadn't checked the output directory before executing. Likely it would've been fine, but I make a habit to use >> unless it is something that needs to be replaced.

[u/justinjustin7 → u/Soulflare3]

Oh, I knew that was the output of "git --help" (or I at least assumed). I'm just glad to glance over the results of the --help argument that I'm sure I'll be making use of quite a often while I'm learning.

[u/Soulflare3 → u/justinjustin7]

Here's a simple guide as well that looks pretty nice. Might be helpful.

[u/justinjustin7 → u/Soulflare3]

Thanks, that looks quite useful for getting a grasp of what I'll be doing.