[ https://issues.jboss.org/browse/TOOLSDOC-306?page=com.atlassian.jira.plug... ] Andre Dietisheim commented on TOOLSDOC-306: ------------------------------------------- Using the server adapter is IMHO the best and simplest way to achieve the upload. It tries its best to hide the complexity of handling git repositories (commit, push etc.). It therefore creates a commit-msg with the following test for you: "Commit from JBoss Tools" and pushes once the commit is done. You can of course alternatively use EGit to push to OpenShift. When we create a new OpenShift application (or import an existing one) we clone the OpenShift git repo to your local machine. The remote repo that we cloned from is still present in the clone. The wizard displays what name it is stored in (*origin*): !git-remote-origin.png! In the *Git Repositories* view ("Git Repository Exploring" perspective) you'll see *origin* in the Remotes: !git-repo-origin-remote.png! EGit offers *Push to Upstream* in the context menu: !git-push-to-upstream.png! Using this action you'll end up doing the very same as our server adapter. Your local commits get published aka pushed to *origin*: !git-pushupstream-origin-remote.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira