01 / 0230 active minuteslocal change

Configure Git Identity And Your Editor

Your Git commit identity is correct, a supported editor is available, and you can verify the separate practice repository and branch where you will learn Git without touching the Passport's background transport.

Work herelocal / powershell or zsh or bash

1Understand
2Do
3Check
4Submit

Learn firstConcept, example, trap and recovery

Outcome#

Concept#

Git records authorship, while GitHub authentication controls repository access. They are separate. A correct identity and a verified branch prevent misattributed commits and changes in the wrong location.

Worked Example#

Git and GitHub CLI are available, GitHub CLI names the intended account, and Git identity is explicit.

A correct example uses these decisions:

What must gh auth status confirm? The intended GitHub account is authenticated.
What should you do before repairing a failed tool check? Read the named check and use its bounded recovery step.

Common Trap#

Changing SSH keys, deleting configuration, or reinstalling everything before reading the exact failed check.

If Blocked#

If the editor is missing, install only the editor; do not clone again. If the remote or branch is wrong, stop and run gh passport doctor. Do not delete the folder, reset Git, replace SSH keys, or paste a token into the remote URL. Use Request help without posting secrets on the passport dashboard if the doctor's named recovery command does not resolve the problem. Submit one sanitized issue and return later; the reviewer does not need to be online.

Useful references:

Understand Before Accepting AI Output#

Do not let an AI assistant insert tokens, rewrite credential helpers, change the remote, or switch branches without explaining the exact reason. Verify the identity, remote, and branch yourself before accepting its claim of success.

Do the mission

One bounded attempt

Pass: 80% + every safety item

Action

Run the read-only tool and identity checks shown below. Fix only a missing name or email through the linked platform guide.

Expected

Git and GitHub CLI are available, GitHub CLI names the intended account, and Git identity is explicit.

Separate practice space

Prepare the repository where you will learn Git

The launcher creates or validates a separate exercise folder. It stops rather than replacing an existing unrelated folder.

Run only the commands for your machine

Step 1windows / powershell

git --version

Expected: A Git version is printed.

Step 2macos / zsh

git --version

Expected: A Git version is printed.

Step 3linux / bash

git --version

Expected: A Git version is printed.

Step 4windows / powershell

gh auth status --hostname github.com

Expected: The intended GitHub account is named.

Step 5macos / zsh

gh auth status --hostname github.com

Expected: The intended GitHub account is named.

Step 6linux / bash

gh auth status --hostname github.com

Expected: The intended GitHub account is named.

Step 7windows / powershell

git config --get user.name

Expected: Your chosen commit author name is printed.

Step 8macos / zsh

git config --get user.name

Expected: Your chosen commit author name is printed.

Step 9linux / bash

git config --get user.name

Expected: Your chosen commit author name is printed.

Step 10windows / powershell

git config --get user.email

Expected: Your chosen commit author email is printed.

Step 11macos / zsh

git config --get user.email

Expected: Your chosen commit author email is printed.

Step 12linux / bash

git config --get user.email

Expected: Your chosen commit author email is printed.

Step 13windows / powershell

git remote -v

Expected: Only expected GitHub remotes appear; no password or token is embedded in a URL.

Step 14macos / zsh

git remote -v

Expected: Only expected GitHub remotes appear; no password or token is embedded in a URL.

Step 15linux / bash

git remote -v

Expected: Only expected GitHub remotes appear; no password or token is embedded in a URL.