The bisect process needs to know which commit is our known bad commit

git bisect bad urhsn47f

If we don't specify the known bad commit it will assume the last commit

git bisect bad

The bisect process needs to know which commit is our known good commit

git bisect good d5b370ec

Shows the difference between the working directory and index (both staged and unstaged files)

git diff HEAD

Shows staged changes

git diff --staged

The alternative command is:

git diff --cached

Opens the file in git console

vim test.txt

When we merge, if there are conflicts and we don't want to finish it, the best way is to abort the operation

git merge --abort

Adds user email for the current local repository (to the local config)

git config --local user.email "tandilashvilivaleri@gmail.com"

After the command execution, In local

config

file located at

.git/config

will be added the following

[user]
        email = tandilashvilivaleri@gmail.com

git config

defaults to

--local

Shows the content of the file to the Git console

cat .git/config

Creates a directory

mygit

inside the current folder and an empty git repository into the newly created folder

git init mygit

It shows all commits in the history of branches, tags and other refs, but it does not show commits that are not reachable from any ref. A typical example of a commit that is not reachable from any ref is when you've just run git commit --amend: the previous commit still exists locally, but it's no longer reachable and won't be shown in git log --all. But git reflog will confirm that it does indeed still exist

git log --all