# Your Branch

### Your default Branch name : 

By default Git will create a branch called *master* when you create a new repository with `git init`. From Git version 2.28 onwards, you can set a different name for the initial branch.

To set *main* as the default branch name do:

```bash
$ git config --global init.defaultBranch main
```

**Checking Your Settings :** 

If you want to check your configuration settings, you can use the **git config --list** command to list all the settings Git can find at that point:

<figure><img src="https://95996732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFPKIHHReZAupZTOQC0WA%2Fuploads%2FaDzdkONuBJsKby6BmiKf%2FGit%20config%20list.png?alt=media&#x26;token=572c51db-db8f-4b67-8d34-15056d560f5d" alt=""><figcaption></figcaption></figure>

You may see keys more than once, because Git reads the same key from different files (`[path]/etc/gitconfig` and `~/.gitconfig`, for example). In this case, Git uses the last value for each unique key it sees.

You can also check what Git thinks a specific key’s value is by typing `git config <key>`:

```
$ git config user.name
Komal Vardhan
```

{% hint style="info" %}
Since Git might read the same configuration variable value from more than one file, it’s possible that you have an unexpected value for one of these values and you don’t know why. In cases like that, you can query Git as to the origin for that value, and it will tell you which configuration file had the final say in setting that value:

```bash
$ git config --show-origin rerere.autoUpdate
file:/home/johndoe/.gitconfig false
```

{% endhint %}