File -> Accounts -> + -> GitLab should solve the problem. Otherwise, contact me using the feedback button on the toolbar (or by email) and I'll be able help you.
I merely cited this as one example of a confusing UI, but this response makes my point even stronger. For most applications, the normal user flow is from general (what the app calls Repository Manager, I guess) to specific (a particular repository). Well-designed user interfaces anticipate the typical user flow and give the user a chance to "go back." For example, a user may accidentally click on the wrong repository. That user likely wants to return the app to its previous state so as to make the correct choice.
Neither of these steps really does that. The first opens a command palette which does not have anything resembling a "go back" command. It does list "Recent Repositories," but there is no reason for a user to assume that "Recent" is the same as All the repositories listed on the first screen. The command palette also omits the folder hierarchy present on the first screen, and that hierarchy may be key to finding the desired repo. Opening a new tab is not at all intuitive for a user that wants to go back. And the most obvious result of the command is a new blank screen.
There a lots of things about Fork that look to be very well-done, and it appears to have a great feature set. But if I'm going to use a GUI instead of the command line for git, then I expect the app to be intuitive and easy to use. For me, Fork is not that. I appreciate that other users may have different opinions, and I do wish the developers great success with the project.
Hi. In Fork you can expand/collapse nodes in the graph. Collapsing all (i.e. --first-parent) and then expanding particular merge commits is also possible.
Good to know. I'm just thinking it might be useful as a default.
I'm also thinking that it's related to that "why didn't Outlook end up using 'subway diagrams'?" question: maybe strict chronological ordering isn't necessarily the best focus for commit ordering with respect to "top-level" merge commits.
Anyway, not a direct criticism of your app specifically, more just a long slow stewing of my own thoughts on the subject that I likely won't ever get around to even prototyping, in case they do congeal into something worth prototyping. You are certainly ahead of me there by having built a thing, and I appreciate that.
Right now I don't think enough people appreciate the idea of --first-parent as a default in as many views as possible (especially as opposed to how many seem to prefer squash/rebase-based workflows solely based on gut reactions to how the "subway diagrams" can look), and I like mentioning that in case it sparks ideas for other people to maybe find workflows that they like more than that (and can take advantage of the 2D nature of the git DAG possibly better than "straight line" approaches).
I'm probably rambling at this point, because yeah I still haven't quite found the right "shape" of this idea and it is interesting to think out loud about it.
Enable 'monospace font in commit description' in Fork preferences and set the guideline for the description width. You can wrap the commit message using the context menu option in the description field.
I've gone ahead and downloaded/installed git-fork and did some brief testing with the features I use most in my existing client. I've sent feedback based on that.
Hi! I develop Fork with my wife. We don't have manager, marketing team, designers, etc. We also don't have meetings which makes us more efficient :). So, we don't need too much money to survive.
Answering your question, yes, it's a one-time purchase which includes future updates. We may release a major paid update in the future, however currently we don't have plans for that. The license is cross-platform. You can activate, deactivate and reassign the license.
Yes, you can lock and unlock LFS files using file context menu. There's also the ability to see the list of locked files (and force-unlock one, if needed).
Excellent, thank you - I’m trialling it now. Loads of positive comments for your product on this thread. High quality paid native Mac software from smaller developers is one of my favourite things about the ecosystem.
Being honest, we don't use LFS internally, so dogfooding doesn't really work in this area. If you don't like something or you have an idea how we can improve LFS support in Fork, please feel free to contact me directly.
Hi. Dan from Fork is here. I guess there's some mistake. I answer a lot of user questions daily and this is the first time I hear about such a feedback. I would really appreciate if you could send me any details (by email or using the feedback button on the toolbar in Fork).
