At long last, you’ve reached the last chapter. This chapter covers the git config command. Its main benefit is to customize the Git commands and tools that you’ve learned over the past chapters. You’ve already used git config in earlier chapters to set or examine specific configurations such as what email address to use for commits (chapter 3) or how git push should behave (chapter 13). You’ve also used git config to create aliases (chapter 9). This chapter focuses on how to modify the behavior of other Git commands to suit your preferences.
Git is a tool, and keeping your Git sharp falls under the habit of always keeping your tools sharp. When your tools are sharp, they’ll always be ready to use when the time comes. In the case of computer tools such as Git, the sharpness of the tool depends a lot on the knowledge and ability of the person using the tool.
The git config command is the key command for advanced techniques with Git. This command lets you create aliases, modify the behavior of certain Git commands, and extend its capabilities. A great many Git features are controlled by Git configuration variables, which git config manipulates, so it’s important to understand what these are, where they’re stored, and how to change them.