Skip to content
GitTree
العربية

Video: Install Git and preview a safe commit identity

The video plays in YouTube’s player, in privacy-enhanced mode.

Check which Git your terminal runs, install it only if needed, and preview a fictional name and email without changing your personal configuration. Then inspect GitTree's identity controls without saving them.

Read the full lesson

The article has every step and command from the video, the practice exercise and the questions.

Go to the lesson

Video transcript

The narration of the video, cue by cue.

  1. Check Git first, then preview an identity without saving it.
  2. A working Git executable and a commit identity solve different problems.
  3. Find the executable your current shell will run.
  4. Now read its version, rather than guessing from an installer.
  5. The inspected GitTree source requires Git two point thirty-nine or newer.
  6. On macOS, choose supported command-line tools or an existing package manager.
  7. Windows users should choose the official installer for their architecture.
  8. On Linux, your distribution chooses the package; verify its version afterwards.
  9. After installation, use a fresh terminal and repeat both checks.
  10. GitTree can recheck discovery after you repair the installation.
  11. A desktop process may discover Git differently from your shell.
  12. The visible Locate control is not a proven working path in this source.
  13. Your name and email become commit metadata, not server credentials.
  14. Author, committer, account and signature are related but different concepts.
  15. Changing configuration does not rename people in existing commits.
  16. Pass the fictional name and email to this one Git command.
  17. The email query prints the value supplied to this invocation.
  18. A command-scoped value is not a saved global setting.
  19. Change only the supplied email. Predict the next result before running it.
  20. The changed input produces Maya's fictional address for this query only.
  21. Repeat the original command, and its supplied email appears again.
  22. Repository settings, global defaults and app profiles persist in different places.
  23. GitTree's injected profiles preserve the repository's own configured identity.
  24. Open Preferences. This is a full-window screen, not a repository operation.
  25. Open Profiles and read where the identity applies.
  26. Injected profiles affect GitTree's commands, not external terminals.
  27. Create an unsaved draft; we will cancel before creating a profile.
  28. Use a clear profile label so this preview is easy to recognize.
  29. Enter GitTree Demo as the fictional commit name.
  30. Enter the fictional address, not your personal account email.
  31. Keep injection mode; leave the signing key and SSH command empty.
  32. Cancel the draft. An open form is not a saved profile.
  33. Return to New Tab with no repository created.
  34. The palette opens Profiles without switching your identity.
  35. Leave again without choosing a different saved identity.
  36. Saving the demo globally could affect unrelated work on this machine.
  37. Repository Undo is not a promised rollback for installation or identity settings.
  38. Verify Git, separate identity from login, and choose where settings persist.
  39. Your check is the two email results and an unchanged profile list.
  40. Next, separate your working files from the snapshot you choose to commit.

All tutorials