reactive-angular-course | How to build Angular applications in Reactive style using plain RxJs - Patterns and Lightweight stat | Reactive Programming library

Cloning a repository copies all ¹ of its commits, and none of its branches.² You don't need branches to have commits.³

After the clone is finished but before returning you to a shell prompt, git clone runs one git checkout; this one git checkout creates one branch. You can go on to create more branches, or—at least for some purposes—just use the names that git clone created, which aren't branch names, but are perfectly good names.

The names that git clone creates are remote-tracking names. If the remote named origin had branches named main, feature/tall, and feature/short, the clone has names origin/main, origin/feature/tall, and origin/feature/short.

The final git checkout step takes one of those names and uses it to create a branch name.⁴ The name chosen here is from your -b parameter to git clone. If you didn't give a -b parameter here, your Git asks the other Git, during the clone process, which name it recommends, and uses that one.

These remote-tracking names show up in git branch -r output. They're not actually branch names, they were just created from branch names, but if all you need is the name, they'll do the job.

¹Technically it copies only the reachable commits. But you can't find the unreachable ones, so you can't tell that it didn't copy them.

²A so-called mirror clone does copy all of its branches. You cannot do any new work in a mirror clone, though.

³You do need names to find the commits, but they need not be branch names.

Curiously, the converse is true: you must have at least one commit to have any branch names. In fact, you must have at least one commit or other internal Git object in order to have any name that is not a symbolic name. (Symbolic names are those that act like HEAD: that hold some other name, typically a branch name. HEAD is normally the only symbolic name you'll see, in part because other symbolic names don't work very well in some versions of Git.)

⁴This is, internally at least, called DWIM mode, with DWIM standing for Do What I Mean (not what I say). That is, you asked git checkout to check out some branch X when branch X does not exist. Rather than immediately giving you an error, git checkout pokes around through your remote-tracking names, looking for an origin/X for instance. If it finds exactly one candidate that looks right, it converts your request to switch to an existing branch, into a request to create a new branch, whose branch-tip-commit is the same commit as the one identified by the remote-tracking name.

It is all very elegant and confusing. 😀 Once you get used to it, it's pretty useful. Then it all breaks when you add a second remote and there are now two remote-tracking names that look like good candidates. Git has recently grown some new facilities to handle this case better, but until you understand DWIM mode in the first place, adding this on will just make things really confusing.