Add push/pull actions

[weihwang]

Proposals to add push/pull actions to the plugin.
https://www.figma.com/file/UyNpeQNuTj6Uv74MoEJDh3ji/Git-extension?node-id=507%3A1156

Pre-requisite
#244 - Surface target branch to inform users before they make a pull/push action.

Option 1
Push/pull actions embedded in a history tab #245 (more overview info for history) to provide context to these actions.

Option 2
Push/pull actions at a high level (icons TBD) to allow push pull with history view, or working environment view.

TASK BREAKDOWN

• Backend for Pull
• Backend for Push
• [] Frontend for Pull
• [] Frontend for Push

[jaipreet-s]

@weihwang

1. Is there an issue for moving the up and trash icons to the right of the main panel?
2. What is the state of the push/pull actions when there is a merge conflict?
3. What is the state of th push/pull actions when there is no upstream defined?

[weihwang]

@jaipreet-s

1. Style of file list #227 is the issue for commit change list styling.
2. Do you know if merge conflicts we can show in the extension? If so, push/pull can be disabled as long as we have a persistent notification of why push/pull is disabled.
3. If we're not supporting creating remote branch/tracking, I think we may need to disable. Otherwise, on pull/push we need to show the terminal for more actions to take.

[tgeorgeux]

Out of the two options above I prefer keeping the push/pull actions exposed as in #2. I don't think it makes sense to make somebody view their git log in order to update their remotes and pull.

[weihwang]

Agree on #2.

[jaipreet-s]

Regarding #2, I would making the push/pull button visible, but disabled, and adding a tooltip to show why they are disabled. There should also be a way to switch to the terminal quickly to see the actual merge conflicts

Regarding #3, @weihwang do we have any mockups which show the state of the push/pull UX in that scenario?

Thanks!

[tgeorgeux]

The final frame of this is showing a fly-out window for details. Do we also have an option that would expand in the sidebar? We don't currently have any fly-out interactions with out sidebars at this point in JupyterLab.

[weihwang]

@tgeorgeux added an inline option. Is there any styling for links, or guidance for icon based actions vs. text?

[brylie]

I like the high-level push/pull buttons. This would be similar to an IDE, showing frequently used Git commands. E.g. Atom Git integration:

[jaipreet-s]

• Backend for Pull
• Backend for Push
• Frontend for Pull
• Frontend for Push

[jaipreet-s]

Released in 0.5