What is the practical value of a bare repository?

Question

git

How is the bare repository used? How is it different from the usual one, except that it saves space on the working tree? You can find the following arguments:

It saves space (do text files take up a lot of space?)
default remote origin is not set (what is the use of this, you have to manually enter it?)
Best practice is to use the bare repository where everyone will push commits.

Is it really the bare repository that is hosted in practice, where all the commits are pushed? Is the saved space worth the opportunity to remotely view the files directly in the browser on the github?

https://www.atlassian.com/git/tutorials/syncing/gi...

Bare repos don't have a working directory so a push will not alter any in progress working directory content.

The running working directory content is just a mirror of the last commit, isn't it? How can we somehow change the in progress working directory content??

Answer 1

bare - just a real repo for shares to others.
It's not about saving space at all.
Git doesn't explicitly store files at all. it saves a snapshot on initialization/adding, and any changes are a set of deltas (diffs).