Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support bare repositories #177

Closed
FredrikNoren opened this issue Aug 31, 2013 · 8 comments · Fixed by #720
Closed

Support bare repositories #177

FredrikNoren opened this issue Aug 31, 2013 · 8 comments · Fixed by #720
Assignees
Labels
Milestone

Comments

@FredrikNoren
Copy link
Owner

Right now ungit crashes (#168) if you try to run it in a bare repository.

@guillaumewuip
Copy link

+1

@mesosteros
Copy link

+1 for this. This feature would allow us to effectively have a sort of personal github/gitlab. It would be really useful for small teams. We'll be using fetch for repos before merging them for now but would appreciate to actually be able so see the commit tree on a bare repository before even fetching it.

@michaelachrisco
Copy link

I am having the same issue with remote repos that may or may not be set up. Some of the errors are resolved if you run ungit --no-autoFetch

@jung-kim
Copy link
Collaborator

Quite frankly, i thought this was fixed. When i do mkdir test; cd test; git init and than going into test director didn't cause any errors for me. What error are you seeing specifically?

@campersau
Copy link
Collaborator

@codingtwinky try git init --bare. For local bare repositories ungits quickstatus just returns "uninited" (no errors).

@Ajedi32
Copy link
Contributor

Ajedi32 commented Mar 10, 2016

Yeah, "bare" is not the same thing as "empty". A bare repository is basically just the .git folder, with no working directory. It's often used on servers where a working directory isn't needed. (So you can push and pull from the repository, but the server doesn't need to a copy of the source at any specific revision.)

@jung-kim jung-kim self-assigned this Mar 14, 2016
@jung-kim jung-kim mentioned this issue Mar 19, 2016
@jung-kim
Copy link
Collaborator

Sorry for my own incompetence that took forever to fix such easy fix.

It is should now support bare repo without any error messages but with disabled staging and stash as it is not applicable to bare repo.

@michaelachrisco
Copy link

Thanks @codingtwinky!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants