Skip to content
GitTree
العربية

Video: Distinguish Git, GitTree and your hosting provider

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

Understand which tool saves history, which one provides the desktop workflow, and which one runs hosted services. You will inspect Git and GitTree without creating the course repository yet.

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. Welcome to GitTree Learn. Build a small page called GitTree Features.
  2. Before creating it, separate three tools often discussed together.
  3. Git records history. GitTree is a workspace. The provider adds services.
  4. Maya edits a headline. Her working file is the current version on disk.
  5. Git can save a selected snapshot with links to previous history.
  6. A local commit needs no GitHub, GitLab, or GitTree account.
  7. That does not save every visible file or upload anything.
  8. We will inspect selected content later. Push is a separate operation.
  9. GitTree shows history and actions using Git installed on your computer.
  10. App preferences and workspaces differ from branches and commits.
  11. GitTree Undo records supported app operations, not every terminal change.
  12. A host keeps a remote and may offer reviews, issues, and checks.
  13. Our main pipeline uses GitLab and a runner on the author's local machine.
  14. The runner executes jobs. GitTree inspects supported results.
  15. A service feature is not automatically implemented by GitTree's adapter.
  16. Read the provider, project, permission, and commit behind each result.
  17. Run git --version. This query changes no repository.
  18. Here Git reports 2.52.0. Your version may differ.
  19. This proves the shell found Git, not that a provider is connected.
  20. In a folder without a repository, run git status --short.
  21. Git says this is not a repository. That negative result is intended.
  22. Missing repository context differs from missing Git. Read the message.
  23. Do not reset, clean, or initialize a random folder to hide it.
  24. The native command catalog is not a list of GitTree buttons.
  25. Open New Tab in GitTree. Do not create the course repository yet.
  26. Open Command Palette, search Feature Guide, and choose that command.
  27. Its default is Alt+H, or Option+H on macOS. Overrides can change it.
  28. Choose Features, search CI/CD, and read the CI/CD runs prerequisite.
  29. Without an open repository, the feature asks you to open one.
  30. Choose Integrations. It also asks for a repository before showing support.
  31. Reading help created no remote, connected account, or pipeline job.
  32. Press Escape. The guide can remember its version as an app preference.
  33. That preference creates no commit. The project still has no graph.
  34. Local Git is Free. Nour, integrations, and drafts need applicable access.
  35. App access, provider credentials, and commit identity remain separate.
  36. A passing job belongs to one commit. An older green SHA is not enough.
  37. Classify a theme change, a local commit, and a runner executing a job.
  38. Confirm that the course project remains uninitialized, with no upload.
  39. Git owns history, GitTree its workspace, and the provider its services.
  40. Next, check installation and identity. Create the repository in lesson four.

All tutorials