> For the complete documentation index, see [llms.txt](https://nkintc.gitbook.io/brainless/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nkintc.gitbook.io/brainless/steam/technology/programs/miscellaneous/git.md).

# git

concept: bare git repo&#x20;

when you type&#x20;

```
$ git clone https://github.com/engineer-man/felix
```

it produces the workspace and the repository. The repository is the hidden directory which is always named `.git` that the program known as `git` uses to create the workspace. The `.git` directory typically looks something like this. &#x20;

```
.
├── HEAD
├── config
├── description
├── hooks
├── index
├── info
├── logs
├── objects
├── packed-refs
└── refs

5 directories, 5 files
```

I have no idea what these are because my understanding of how git works is superficial at best.&#x20;

git bare repo&#x20;

A git controlled repo has two parts: a hidden `.git` folder which contains the files which the program `git` needs to function to recreate the workspace, which is the other user side component. using the function-command

```
$ git clone --bare [fileName1] [fileName2]
```

this is a three state system because there are two clone processes

* original repository&#x20;
* bare repository
* git version controlled repo

really useful in creating a new project which is based in large part from another repo

this bare repo can be used a shit-fuck-undo return to save so keep it in a safe place&#x20;