(progit, p.27) Git comes with a tool called git config that lets you get and set configuration variables that control all aspects of how Git looks and operates. These variables can be stored in three different places:
- [path]/etc/gitconfig file: Contains values applied to every user on the system and all their repositories. If you pass the option —system to git config, it reads and writes from this file specifically. Because this is a system configuration file, you would need administrative or superuser privilege to make changes to it.
- ~/.gitconfig or ~/.config/git/config file: Values specific personally to you, the user. You can make Git read and write to this file specifically by passing the —global option, and this affects all of the repositories you work with on your system.
- config file in the Git directory (that is, .git/config) of whatever repository you’re currently using: Specific to that single repository. You can force Git to read from and write to this file with the —local option, but that is in fact the default. Unsurprisingly, you need to be located somewhere in a Git repository for this option to work properly.
git config --list --show-origin: Showing all git config and whe this config locatedj
git config --global core.editor "code --wait": Config vscode as code editor
git status -s: short ver of git status
git rm --cached file_name: remove file from staging area
git checkout -- filename: Discard change in filename
git remote -v: shoing remote
git remote show origin: show infor on remote origin
git push -d <remote_name> <branchname>: delete branch on remote host