-
Notifications
You must be signed in to change notification settings - Fork 84
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
[BUG] Nothing shown after cloning a repository #258
Comments
Hi @BenEngbers, could you attach a screenshot of the issue? Take into account that if the repository has no commits yet, it won't show antything. You will have to commit at least once to see the treeview. |
Also, I've checked in the case of a cloned empty repo, and since there are no commits, the branch master cannot point to any SHA and therefore is not shown. Unfortunately for the GUI, this is how Git actually works. |
Sorry for the delay, I have been away a few days. After a reboot, I have tried to clone a client for basex (https://github.com/JohnLeM/BasexCPPAPI.git). In ~/Git a directory BasexCPPAPI is created but nothing else happens. My personal github-page shows that I am logged in. Ben |
I'll take a look through that screen. I realize now that I've tested it locally but with master, so it might be that I already fixed this hehe. I'll checkout 1.5.0 to see that I can reproduce it and then double-check master 😄 Thanks for the report! |
@BenEngbers I finally had time to dig into this. I found the issue and I'm right now fixing it :) |
I'll prepare a new release with all the changes so far. |
Describe the bug
After cloning a repo from github a status-bar pops up indicating that a repository is loaded. Locally a directory for the clone is created but nothing happens
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect to see a tree-view from the master
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: