![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 6 Jul 2007 02:19:33 +0000 (22:19 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 6 Jul 2007 08:02:02 +0000 (04:02 -0400) | ||
| commit | 87b49a533b0ee0da06c06fb466844885ae0d35bd | |
| tree | 394247a67b9726644a312a66ad38d0025a1c9e12 | tree | snapshot |
| parent | 840bcfa7b55dd94bd97a2d19a250f38d9ce80c77 | commit | diff |
git-gui: Include a Push action on the left toolbar
Pushing changes to a remote system is a very common action for
many users of git-gui, so much so that in some workflows a user
is supposed to push immediately after they make a local commit
so that their change(s) are immediately available for their
teammates to view and build on top of.
Including the push button right below the commit button on the
left toolbar indicates that users should probably perform this
action after they have performed the commit action.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Pushing changes to a remote system is a very common action for
many users of git-gui, so much so that in some workflows a user
is supposed to push immediately after they make a local commit
so that their change(s) are immediately available for their
teammates to view and build on top of.
Including the push button right below the commit button on the
left toolbar indicates that users should probably perform this
action after they have performed the commit action.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui.sh | diff | blob | history |