Video: Create your course repository, then distinguish clone and open

Video transcript

The narration of the video, cue by cue.

1. Create the course repository, then separate cloning from opening.
2. Use a reserved parent folder outside existing source repositories.
3. Initialize new history, clone a separate repository, or open an existing one.
4. Start inside GitTree on the New Tab screen.
5. Choose Init. Review the dialog before creating anything.
6. Enter the full path to the new gittree-features folder.
7. The native folder chooser is an alternative; recheck the final location.
8. Choose main explicitly instead of relying on a machine default.
9. Keep bare mode off because this project needs working files.
10. Decline both optional templates to preserve the empty checkpoint.
11. Keep Open after creating enabled, then review every choice.
12. Initialize once and wait for the actual repository result.
13. If trust review appears, read the findings before granting trust.
14. The original exists, but its first commit does not.
15. HEAD can name main before main has a commit to point at.
16. Open this repository's Preferences page, not the global Profiles page.
17. Check the write target before typing the fictional identity.
18. Apply GitTree Demo as this repository's commit name.
19. Apply the fictional email at the same local scope.
20. Enter can apply a field too. Exit only after both writes succeed.
21. Check that you are inside the original working tree.
22. The bare-repository check must be false.
23. The symbolic branch check should print main.
24. No commit resolves yet. Silent exit one is expected here.
25. These three inspections should produce no output.
26. Read only the two local identity values, not private global settings.
27. Native Git can initialize too, but do not reinitialize the app-created original.
28. Now copy this same empty repository into a separate local folder.
29. Open Clone and use the URL path rather than a provider account list.
30. Use an absolute file URL for the original, not a raw local path.
31. Name the destination explicitly and confirm it is not the original.
32. Keep the full-history defaults and leave advanced clone options off.
33. Run the clone and let the actual progress finish.
34. An empty source produces a copy without commits; that can still succeed.
35. The empty-repository warning is not a failure by itself.
36. The copy has origin and an unborn main, not a hosted pipeline.
37. Cloning did not copy the original's local commit-name setting.
38. Origin belongs to the copy. The original did not gain a remote.
39. Open the original again before continuing the course.
40. Dropping the existing folder is another way to open it, not clone it.
41. Check the original again: no remote, no commit, and the local demo identity.
42. A separate initialization with trunk reports trunk, still without a commit.
43. A destination refusal protects existing content. Choose a new folder.
44. If a clone fails or is cancelled, read what cleanup actually retained.
45. Undo and reflog are not promised rollback for initialization or identity settings.
46. Init creates metadata, clone creates a copy, and open selects existing data.
47. Verify the original's state before adding the first files.
48. Next, create the hero and make the first deliberate commit.