Hacker News Reader

Comment by nailer | Hacker News Reader

After trying new GitHub Desktop Beta mentioned in the article a week ago: it's still nowhere near compete enough to work:

- You can only stage all changes in a file - so you can't discard 'console.log('Wooo'); debugger;' when committing, you have to remove those in your editor first, then commit.

- you can't reverse commits. Need to roll HEAD back to a previous commit, push those fixes, then resume what you were working on? You can't do it.

- still no graphical interactive rebase to merge and squash and reorder commits (the main reason people put up with sourcetree).

It feel fast and responsive though.

Edit: downvotes seem odd. If you think this is offtopic, the GitHub Desktop Beta is announced in the article.

View on HN

> You can only stage all changes in a file

If I'm understanding you correctly, this is wrong. You can add individual lines in a file to your commit. That's one of the main uses I have for the app: it's easier to split up file changes between commits than on the command line. See this screenshot: http://imgur.com/a/4CQG7 You have to click on the line numbers to add/remove individual lines.

Not a very obvious UI!

SourceTree is much better in this regard.

UI is same as Tower. Doesn't seem that far off for me.

No, Tower works differently (unless it has changed in the few months since I used it). In Tower, you can select lines by clicking line numbers, but then you must click "Stage" to actually stage those lines. Then your selection is cleared and those lines are moved to a separate "Staged" tab for that file. Whereas with GitHub Desktop, just selecting the lines marks them as lines to be staged. (GitHub Desktop doesn't actually run `git add` on those lines until the moment you click "Commit".)

Well, fortunately it's free and open source: https://github.com/desktop/desktop

You could submit an issue or a pull request with suggestions on what a more obvious UI might be!

Looks exactly the same as the previous GitHub Desktop app.

Thanks! It took me a while to work out how to do this even reading your description.

- First I thought you select lines, like other git apps. No, it's not just that numbered line, it's the actual digits on the left.

- Then I selected some digits, expecting a 'stage' button to appear.

Then finally I realised just selecting the lines committed only them.

Even working out how to do it, it's still weird because lines with blue digits now get committed, lines with green ones don't.

These sound like advance features that you can easily drop down to the CLI for.

They're pretty common for me, but how are advanced usage and using a CLI related? These seem orthogonal to me.

Reply on news.ycombinator.com