Before you start#
Git is version-control software: it records file versions. A repository is a project folder with history; a clone is its separate local working copy. GitHub stores the shared online copy; GitHub CLI (gh) acts through your login.
| Setting | Purpose | Inspection |
|---|---|---|
| GitHub login | Authorizes GitHub actions | Which account gh uses |
| Git author identity | Labels commits with name/email | Effective values and their configuration source |
| Branch and origin remote | Select work and its online repository | Prepared practice branch and credential-free URL |
A correct login does not set the commit author. A remote address must not contain a password or token. The repair below changes author identity only in this clone. GitHub Education is an optional student benefit application; waiting for approval does not block this Git practice.
Inspect all three settings before changing one. If the login is right but the author is wrong, which repair would address the actual problem?
Separate login from commit authorship
Keep the intended GitHub account. Confirm the effective name/email from the practice clone, then use its local identity repair only if needed. Inspect the branch and origin independently. Do not reset another project to match this one.
Repair the specific setting that failed, inside the practice repository.