Live data from Hacker News

Fork: Fast and Friendly Git Client for Mac

git-fork.com

81–90 of 109 posts

Re: Fork: Fast and Friendly Git Client for Mac

#81

For an open source alternative, remember there's also the forked version of GitX: https://rowanj.github.io/gitx/

This. I can't really tell how much time of doing "git commit -p" GitX has saved me. It's a much easier way to visualize, stage and group changes into commits when you've made a bunch of unrelated changes.

Re: Fork: Fast and Friendly Git Client for Mac

#83
Reminds me of gitx (a good thing!) :)

Is there a way to only view commits that belong in the current branch (like git log)? The commits from the other branches are distracting when you're trying to read the history of a particular branch.

Re: Fork: Fast and Friendly Git Client for Mac

#84
post #61

Earlier quoted context omitted.

Hi. Didn't even think about such a requirement. In next version I'll make credentials optional (with a warning though).

People shouldn't use git without having configured that. It would prevent incorrect commits landing in public repositories. Actually git defaults to some made-up local git author if it's not set, and that's less useful and sometimes invalid, provoking git-fsck errors.

Git explicitly shows a "Committer" line when typing the commit message if it chooses a default, so I also find not setting one globally and getting this reminder to be more useful:

  # Please enter the commit message for your changes. Lines starting
  # with '#' will be ignored, and an empty message aborts the commit.
  #
  # Committer: Ben Alpert 
  #
  # On branch master
  # Your branch is up-to-date with 'origin/master'.
  #

Re: Fork: Fast and Friendly Git Client for Mac

#85
post #9

The only thing that jumps out at me is the visual of the git tree diagram on the left - other than that why not just use the command line? Am I missing something?

Because when you're doing anything outside of git commit am- "whatever" it's nice to be able to see the complete implications of your actions, what files have been modified, what lines in those files have changed, etc.,

git commit -v gives you the diffs provided you don't also use -m. Personally, I find -m to be a dangerous flag for commit for exactly the reasons you described not mention its hard to really do detailed multi-line commit messages with -m.

Re: Fork: Fast and Friendly Git Client for Mac

#86
post #9

The only thing that jumps out at me is the visual of the git tree diagram on the left - other than that why not just use the command line? Am I missing something?

When you use a git GUI some console actions can be made easier: - I can stage/unstage/reset my changes line-by-line - I can observe the whole repository structure as it was at the moment of commit - Gui client automatically keeps my submodules in the valid state so I don't need to check their state after each checkout - I can quickly review the whole repo history (sometimes it can be useful when I am involved in a ne…

All of these things are readily available from the native interface. Hmmm... Maybe a GUI man page browser could replace hundreds of these projects...

Re: Fork: Fast and Friendly Git Client for Mac

#89
post #54

Earlier quoted context omitted.

I already got that question today. So, I'll just repost my answer: here are some differences from the top of the head: * Fork has tabbed interface * For each commit you can see not only changes, but also the whole repository as it was at the moment of commit * Diff viewer shows exact difference between two pieces of code. For example, here are both SourceTree and Fork showing the same commit: https://dl.dropboxuserco…

SourceTree has a tabbed interface as well now. The diff viewer might be interesting if it's really good but I think that to require an external viewer where the company focused on that as a product. On Mac most of the good options are paid though, might help you.

All of the OS X interfaces to Git are, to be honest, quite terrible. Sourcetree is awful. GitHub Desktop is even worse. I've tried a couple of others, the names of which elude me at the moment. I think most of it is less of a complaint against the software itself, and more of a problem with trying to present the complexities of Git in a simplistic UI. The simple fact is: Git as a whole is really, really freaking complex. Making the basic operations idiot proof is difficult enough, and then you have to try to offer a frontend for things like rebasing. Seriously though, fuck the products that pre-select all unstaged files to be added to the index on every commit. If I wanted the file staged, I would add it. Stop harassing me to add my development files - and no, I shouldn't have to gitignore them to prevent being constantly forced to deselect them. By all means, show checkboxes for me to add the files, but do not pre-check them.

I haven't seen a single interface that gets it right. JetBrains' integration in their IDEs is the closest to "mostly usable" I've seen, where branch creation, pulls, merges, conflict resolution, and pushes are fairly straightforward. It's still far from perfect - I do the lower-level Git > Pull rather than using the Update Project window because I have no idea what operations that window performs; and some rare operations still require dropping to command-line. I'd rate their implementation a 7/10 compared to the 3/10 other tools like Sourcetree provide.

A huge reason JetBrains has an insurmountable lead is its diff and merge editor. It is the best on the market, and the only usable side-by-side merge tool I can work with. Their 3-way diff is a dream to use. The last time I had to assist a co-worker merge a conflict using WinMerge on Windows, I gave up after 30 minutes. I flat out could not understand what the differences were, let alone figure out how to resolve the conflicts. Went back to my desk, checked out the branch in JetBrains' PhpStorm, performed the same merge, and had the conflicts resolved in a couple of minutes. It's no surprise to me that people using WinMerge erase work done by other people far too often.

Anti-disclaimer: not affiliated in any way with JetBrains. Their IDEs are mostly amazing, though it's frustrating that they focus 95%+ of their efforts on new features without going back and fixing what is wrong with their existing features. Their diff/merge editor, at least, is unmatched by any other product I have seen to date (other than the fact that CMD+F / CTRL+F to find in the diff editor is broken... again, JetBrains has some serious bugs that never get fixed).

Re: Fork: Fast and Friendly Git Client for Mac

#90
post #33
post #2

This looks sweet! I use git quite lightly right now as I'm currently the only developer on my project. Gitup.co is the benchmark of Git apps for me right now. I barely need anything more than it and it's so incredibly light feeling. Like the app goes out of the way so that I can do what I need, such as reviewing lines to be staged. It hasn't been receiving many updates unfortunately. I'm happy that another app has po…

Another gitup user here. What kind of updates were you hoping for? Seems pretty solid to me.

Looking at the website I see there's quite a few features I didn't know about! Maybe there's not really any update I would need after all.
Post reply on HN