7. Git Алатки
- 7.1 Revision Selection
- 7.2 Интерактивно стажирање
- 7.3 Stashing and Cleaning
- 7.4 Signing Your Work
- 7.5 Searching
- 7.6 Rewriting History
- 7.7 Reset Demystified
- 7.8 Напредно спојување
- 7.9 Rerere
- 7.10 Дебагирање со Git
- 7.11 Submodules
- 7.12 Збивање
- 7.13 Заменување
- 7.14 Складирање на ингеренции
- 7.15 Заклучок
A3.1 Appendix C: Git команди - Setup and Config
Throughout the book we have introduced dozens of Git commands and have tried hard to introduce them within something of a narrative, adding more commands to the story slowly. However, this leaves us with examples of usage of the commands somewhat scattered throughout the whole book.
In this appendix, we’ll go through all the Git commands we addressed throughout the book, grouped roughly by what they’re used for. We’ll talk about what each command very generally does and then point out where in the book you can find us having used it.
Setup and Config
There are two commands that are used quite a lot, from the first invocations of Git to common every day tweaking and referencing, the
Git has a default way of doing hundreds of things. For a lot of these things, you can tell Git to default to doing them a different way, or set your preferences. This involves everything from telling Git what your name is to specific terminal color preferences or what editor you use. There are several files this command will read from and write to so you can set values globally or down to specific repositories.
git config command has been used in nearly every chapter of the book.
In First-Time Git Setup we used it to specify our name, email address and editor preference before we even got started using Git.
In Git Алијаси we showed how you could use it to create shorthand commands that expand to long option sequences so you don’t have to type them every time.
In Ребаза we used it to make
--rebase the default when you run
In Складирање на ингеренции we used it to set up a default store for your HTTP passwords.
In Keyword Expansion we showed how to set up smudge and clean filters on content coming in and out of Git.
Finally, basically the entirety of Git Configuration is dedicated to the command.
git help command is used to show you all the documentation shipped with Git about any command.
While we’re giving a rough overview of most of the more popular ones in this appendix, for a full listing of all of the possible options and flags for every command, you can always run
git help <command>.