# git concept: bare git repo when you type ``` $ 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. ``` . ├── 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. git bare repo 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 * 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nkintc.gitbook.io/brainless/steam/technology/programs/miscellaneous/git.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.