That's because there's not one.
A bare repository doesn't have a working copy, which is not typically what people want in a user-focused repository, seeing as it makes most of the GUI operations pointless (Commit, Checkout, Merge, Pull, for example).
Furthermore, if you know enough about what you're doing to know what --bare means, then you know enough to launch the terminal and write the clone command yourself. There are enough "computer illiterate" SourceTree users that providing a bare option in the GUI would be a BAD idea. ("I just cloned my repository, but I only have a .git folder!! Where are my files?!?! UNINSTALL!!!111") Those folks aren't going to "accidentally" go to the command line and "accidentally" add --bare to a valid clone command.
I see. Thanks for the quick answer. Well, I won't waste your time with an explanation as to why I want to create a bare repository. It's not important as I understand what you're saying from a UI design standpoint. On the other hand a simple ability to add git options (for those with such understanding) to a clone command would've made the question unnecessary.
Yes, I can do it with the command line interface. Unfortunately, I'm being greeted with authentication request when my key has no password. Guess I need to resolve that issue first.
Thanks again, Seth.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs