[
https://issues.jboss.org/browse/JBIDE-14018?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-14018:
------------------------------------------
The suggestion with the dialog looks like a very valid and silmple approach to me.
Nevertheless to improve the current situation the following could help:
* list the commits while showing the actual changes ("git log --name-status" or
"Team->Show in History" which shows the full history and you can inspect the
changes by selecting the individual commits)
* Commit and Push via EGit: Use the "Git Staging" view to commit. Pushing would
also work via "Git Staging" ("Commit and Push" button) if
"origin" is pointing to OpenShift. If not, you can use the fully fledged push
from EGit via "Team->Remote->Push...". I wrote an extensive blog-post
which outlines how to use EGit here:
https://community.jboss.org/en/tools/blog/2013/06/18/how-to-use-eclipse-e...
OpenShift commit message references JBoss Tools
-----------------------------------------------
Key: JBIDE-14018
URL:
https://issues.jboss.org/browse/JBIDE-14018
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Michelle Murray
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 4.2.x
Attachments: commit_from_JBT.png, Customized Git Commit on Publish.png
In Servers tab, when you right-click on an OpenShift server adapter and click Publish, an
automatic commit message is generated: "Commit from JBoss Tools".
This message references JBoss Tools - for JBDS it should mention JBDS. I realise it is
difficult to have a different message for JBT and JBDS so I guess the message needs to be
changed to not reference either.
--
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