Add Stage All and Unstage All buttons in git panel

[kuychaco]

Fixes #119

/cc @simurai for design 💭

[simurai]

Awesome! This will save so many clicks. 🎉

Changed the buttons to be a bit more subtle:

Does it need keyboard support? It could be part of the tab cycle or have its own keybinding. Currently you can stage/unstage all with cmd-a + enter, maybe ok.

[kuychaco]

Does it need keyboard support? It could be part of the tab cycle or have its own keybinding. Currently you can stage/unstage all with cmd-a + enter, maybe ok.

Yeah I think cmd-a + enter should be good enough to cover keyboard support while the focus is in the git panel, and that way we can keep the tab cycle tight.

On a related note, @smashwilson brought up a good point that having Atom-level commands for stage/unstage all on the workspace could be handy and save the user from having to first focus the git panel. They can do github:stage-all and then github:commit from anywhere in the editor. Question is - does it make sense to bind these to keyboard shortcuts? If so, which keys? /cc @simurai for 💭

[smashwilson]

Awww you didn't go with github:shotgun 😉

[simurai]

They can do github:stage-all and then github:commit from anywhere in the editor.

Yessss.. 💯

Looking at #174, ctrl-7?

[kuychaco]

Looking at #174, ctrl-7?

Hmm maybe. But perhaps we'll want to reserve that for other potential panels (like a config panel?). I think for now I'll just merge without keybindings and the user can do the binding themselves if they like. And we can always add a default binding in the future if we decide it's a good idea.

[shelldandy]

@kuychaco how can I add a default binding for stage/unstage all? thanks a lot!

[kuychaco]

@Mike3run here's how you can add a default binding for stage/unstage all:

1. open your keymap file (via application menu or in command palette type "Open Your Keymap")
2. add something like the following

'atom-workspace':
  '<some key combo>': 'github:stage-all-changes'
  '<some other key combo>': 'github:unstage-all-changes'

Refer to the following documentation for more details on keymaps in-depth: http://flight-manual.atom.io/behind-atom/sections/keymaps-in-depth/

Hope this helps!

[shelldandy]

Thanks a lot @kuychaco