Features to be added to the `git commands` section.

[HarshKapadia2]

• [ ] Plumbing and porcelian commands
• [ ] To show commit SHA1 of HEAD git rev-parse HEAD
• [ ] git gc --aggressive commands.
• [ ] Git LFS (large file system)
  • Conditions for large files on GitHub
  • Storage and Bandwidth Usage
  • Atlassian Git LFS overview (Also, the video at end of this article is a good watch.)
  • Official Git LFS page
  • Migrate history to or from Git LFS
  • Alternative way: Split files into multipart zip archive, then either use a Git Hook or a prebuild step to combine and unzip the files.
• [ ] Removing Accidentally Committed Files From Remote History

[HarshKapadia2]

• [ ] git rebase
  • [ ] Short guide
  • [ ] Add git pull --rebase to git pull and reference it in git rebase. (Optional reference)
  • [ ] Merging vs Rebasing
  • [ ] git rebase --continue (--quit and --abort)
• [ ] Patches
  • Create a patch file from git diff
  • Creating and applying a patch
  • If the patch is a commit, then just run git am file.diff.
  • If the patch is not a commit, then run git apply file.diff and then git am file.diff.
  • .diff can be .patch as well.
  • Decoding a patch in base64 format

[HarshKapadia2]

Add all info from the following articles:

• [ ] https://medium.com/mindorks/what-is-git-commit-push-pull-log-aliases-fetch-config-clone-56bc52a3601c
• [ ] https://dev.to/lydiahallie/cs-visualized-useful-git-commands-37p1

[HarshKapadia2]

Under the git command in this section, add:

• [ ] git version
• [ ] Git update command

[HarshKapadia2]

• [ ] Atlassian article on Git submodules

[HarshKapadia2]

• [ ] git revert
• [ ] git restore
  • [ ] General details
  • [ ] -s flag
• [ ] git reset (+ add commands from #75, although it is meant for #10)

[HarshKapadia2]

• [ ] Under git commit, add the -s (--signoff) flag.
  • Article # 1
  • Article # 2
  • Check out DCO in relation to -s

[HarshKapadia2]

• [ ] Add the git cherry-pick command.

[HarshKapadia2]

• [ ] Under git checkout, add the --orphan flag.
  • Ref article
  • Add the flag, give an explanation on what is does and its need.
  • git rm -rf or git reset --hard might be required (beware of the file not in .gitignore though.) (source)

[HarshKapadia2]

• [ ] Under the --amend flag in git commit, add the --no-edit option.
  • Explain that files can be forgotten to be committed or be committed by mistake & add the two cases of amending a commit (to change the commit msg/descp and/or add/remove a file) to the common mistakes and how to solve them (#10) sub-section.
• [ ] git commit --no-value option
• [x] Add --author "Full Name <[email protected]>" option to git commit.

[HarshKapadia2]

• [ ] Add a --staged flag to the git diff command.
• [ ] Add the git mv command.

[HarshKapadia2]

• [ ] Co-authored commits
  • (I had to use a text editor to write the commit msg as pressing the enter key in cmd executes the command.)
  • https://github.blog/2018-01-29-commit-together-with-co-authors/
  • https://medium.com/blackode/creating-co-authored-commits-on-the-command-line-git-305ae2af9f73

[HarshKapadia2]

• [ ] Add set-url option to git remote
  • https://www.git-scm.com/docs/git-remote

[HarshKapadia2]

• [ ] git shortlog
  • Add details on git shortlog from this as well: https://github.blog/2020-10-19-git-2-29-released/

[HarshKapadia2]

• [ ] Contextual git push and git pull. (Find context using git branch.)
  • Executing just git push instead of git push origin main to push code to the main branch.
  • Might not work the first time as the upstream is not set. Use git push -u origin main the first time.

[HarshKapadia2]

• [x] Add git config --global init.defaultBranch <branch_name> to the git config sub-section.
  • This is to combat the new default main branch on GitHub.
  • Add note that this is only for GitHub and might cause problems with other services like GitLab.
  • Refer to this comment of issue #47.

[HarshKapadia2]

• [ ] From image below make the following changes to the git branch sub-section:
  • Make necessary changes to -m option in web site.
    • Check if what already exists is correct and accordingly make changes.
  • Add -u flag.
  • Add references to the branch renaming section if necessary. (The section is supposed to be added as per a comment in issue #21.)

[HarshKapadia2]

• [ ] Add git reflog documentation
  • Write about force pushing (Add note: changes history and can cause a lot of problems)

[HarshKapadia2]

• [ ] Add commands from issue #70.
• [ ] Add git fsck

[HarshKapadia2]

• [ ] Add --author="<regular_exp>" to git log (Ref article)
• [ ] Add pretty formats to <?>
  • Can be used by multiple commands?
  • Eg: git log --pretty="format: %h %aN"
  • A pretty format list can be found in Atlessian's git show article as well.
• [ ] git format-patch

[HarshKapadia2]

• [ ] Add the -A option to git commit and note the difference between -a and -A.
  • 10 Must Know Git Commands That Almost Nobody Knows

[HarshKapadia2]

• [ ] Add directory option to git clone.
  • Eg: git clone <url>.git <dir_to_clone_into> or git clone <url>.git . (Same directory, will not create a new directory to put the files in.)

[HarshKapadia2]

• [ ] Changing the default Git editor.
  • git config --global core.editor "<editor_name>"
  • VS Code: git config --global core.editor "code --wait" (Article)
  • Others: (Article)

[HarshKapadia2]

• [ ] Add info about git tag.
  • [ ] Pushing a tag to a remote repository
  • [ ] Deleting Local and Remote Tags
  • [ ] Git Tag Explained: How to List, Create, Remove, and Show Tags in Git (esp add git show - add next point first)
• [ ] Add git show

[HarshKapadia2]

• [x] Add git add -p

[HarshKapadia2]

• [x] #85

[HarshKapadia2]

• Merge conflicts: #94

[HarshKapadia2]

• [ ] Multiple Branches in Git (git worktree)

[HarshKapadia2]

• [ ] Bare Git repositories
  • What is a bare repository and why would I need one?
  • all about "bare" repos -- what, why, and how to fix a non-bare push
  • What's the -practical- difference between a Bare and non-Bare repository?