On Wed, Feb 19, 2020 at 10:03:04AM +0200, Andrei POPESCU wrote: > On Ma, 18 feb 20, 12:25:40, john doe wrote: > > > > Don't forget that the repositories on a server/remote repositories are > > to be 'bare' and 'ending with '.git'. > > Using a bare as remote has some advantages in case you don't actually > need a working tree "there", it is however not a requirement.
No, but still highly recommended. Pushing to a non-bare repo is... possible but finicky (a non bare repo has always a "checked out" branch: now imagine that one isn't clean. What's to happen? See e.g. [1] for some discussion. I'd recommend: always use bares as remotes (unless you really know what you're doing -- or equivalently: unless you're into... learning). Cheers [1] https://stackoverflow.com/questions/1764380/how-to-push-to-a-non-bare-git-repository -- t
signature.asc
Description: Digital signature
