I want to find a way for my bare repository (which acts as my remote that I host on my own server computer) to store the actual working files as a working file, not the compressed version when I push them in.
Hi Yordan, welcome to the Community!
This question is not about any Atlassian product, but about how Git works. If you want actual working files, then you need a working repo, not a bare one:
What is the difference between a repository created using the
git initcommand and the
git init --barecommand?
Repositories created with the
git initcommand are called working directories.
Repositories created with
git init --bareare called bare repos. They contain no working or checked out copy of your source files. They store git revision history of your repo in the root folder of your repository instead of in a .git subfolder.
Why use one or the other?
Well, a working repository created with
git initis for… working. It is where you will actually edit, add and delete files and
git committo save your changes.
A bare repository created with
git init --bareis for… sharing.
I extracted that definition from What is a bare Git repository, I recommend reading the full article for a better understanding.
Hope that helps!
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events