![]() Global configuration values are stored in a file that is located in a user’s home directory. The global level configuration is user-specific, meaning it is applied to an operating system user. Local configuration values are stored in a file that can be found in the repo’s. The local level configuration is applied to the context repository git config gets invoked in. The following configuration levels are available:īy default, git config will write to a local level if no configuration option is passed. The git config command can accept arguments to specify which configuration level to operate on. git config levels and filesīefore we further discuss git config usage, let’s take a moment to cover configuration levels. This will return the configured name if any, that Git will associate with locally created commits. In this example, the name is a child property of the user configuration block. It can easily be fixed.įor e.g: This is what our working tree (directory) looks like: If you ever find that you accidentally left something out of your last commit, be it a file or an extra change to a file that you just committed, don’t worry. Git has a number of awesome features Not least of all is the ability to amend the previous commit. This combination immediately creates a commit of all the staged changes and takes an inline commit message. git commit -am “commit message” : A power user shortcut command that combines the -a and -m options. ![]() Passing the -m option will forgo the text editor prompt in favor of an inline message. By default git commit will open up the locally configured text editor, and prompt for a commit message to be entered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |