Panics on bare repositories

[etrianag]

Describe the bug
Unable to execute gitui inside a bare repo.

To Reproduce
Steps to reproduce the behavior:

1. git init --bare test-repo
2. cd test-repo
3. gitui
4. See panic message

Expected behavior
May be a message: Sorry no support for bare repos

Desktop (please complete the following information):

• OS: Kubuntu 20.04

Additional context

• Shell: Bash

[extrawurst]

Hi @etrianag thanks for your interest in gitui. This is definitely not solved elegantly, I will make that a better error message for now and not support bare repos for the time being. is there a significant use case for a tool like gitui inside bare repos to make this a feature request to support them?

[extrawurst]

should print this now:

invalid git path
please run gitui inside of a valid git (non-bare) repository

[etrianag]

Normally, I don't use bare repos, but by chance, the most recent repository I used, was a bare repo, because I was setting it to handle my dotfiles, and today a found this program, and giving my first try, it was natural to test in my last repo, so I discovered the problem. Just reported to improve gitui.
By the way, I checked in a normal repo, with a lot of commits, and I'm impressed with it: good job!.
So, I will not consider making gitui "bare repo" compatible, at least in my opinion, a feature request.
I'm not english native, but I suggest to change the message a little, because a bare repo, is a valid git repo.

An off topic question: It would be useful to add a cli option like -v, to see the version, ie: "gitui -v". Or maybe "gitui --help" to show usage. (I don't know if creating issues for simple things, like this question, is good or not for the project).

Thanks for responding so quickly, and congratulations by this project.

[extrawurst]

regarding the wording, you are right, I will rephrase it👍

the version command line arg is actually in master already (since of #88) and will roll out in the next release:

gitui --version
gitui 0.4.0

[jtrv]

Could we reopen this issue as a feature request and at least keep it in the backlog?

I store my dotfiles in a git bare repository, and many of my friends do as well. Lazygit already has this feature and it's pretty much the only thing that keeps me from switching to Gitui as my default. Using lazygit for my dotfiles was actually how I got comfortable with lazygit and began testing and learning about some of the more advanced functionality. It really improved my understanding and knowledge of lazygit and git as a whole.

Interaction with git bare repositories would give Gitui more feature parity and open it up as a way for others like me to practice and get used to the tool with their dotfiles before using it in production.

[extrawurst]

Well this ticket is part of the backlog :)
If you ever feel like it come and join me by contributing this feature, I’d for sure take it.

[mmahmoudian]

@JacobTravers Thanks for the Lazygit 👍 I played with it for few minutes and seems it matches my needs regarding bare repos. I'm not a big fan of Go, but functionality comes first.

[revred]

not support bare repos for the time being. is there a significant use case for a tool like gitui inside bare repos to make this a feature request to support them?

I am trying to use git as a no-sql local database. Support to this feature is going to be a critical decision in choosing the git client. Could I request for this feature and if a tentative timeline can be provided, please?

[basbebe]

Bare Repos are often used Tonfall dotfiles.
Tools like yadm also use this method

[extrawurst]

i am Open for contributions.

For the time being, Lazygit provides this: #100 (comment)