Git stores author information so that when you're making a commit it can track who made the change. Here's how you might update your global Git configuration (don't do this yet):
git config set --global user.name "ThePrimeagen"
git config set --global user.email "[email protected]"
Let's take the command apart:
git config: The command to interact with your Git configuration.set: The subcommand to set a value – i.e., to add it if it doesn't already exist, or update it if it does.--global: Flag stating you want this configuration to be stored globally in your ~/.gitconfig. The opposite is --local, which stores the configuration in the current repository only.user: The section.name: The key within the section."ThePrimeagen": The value you want to set for the key.Again, this course requires a git version of at least 2.46.0. See chapter 1, lesson 2 for instructions.
In earlier versions of the Git CLI, the config interface used flags like --get, --set, and --list. Those older-style commands still work, but you may see deprecation warnings.
You can actually store any old data in your Git configuration. Granted, only certain keys are used by Git, but you can store whatever you want.
Set the following useless key/value pairs in your local Git configuration for the Webflyx repository (omit the --global flag to set them locally):
webflyx.ceo "ThePrimeagen"webflyx.cto "TheLaneagen"webflyx.valuation "mid"Git has a command to view the contents of your config:
git config list --local
You can also just view the contents of your local config file directly:
cat .git/config
Run and submit the CLI tests.