[
https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-13175:
------------------------------------------
There are actually 2 conditions that determine whether there are local changes that can be
published:
1) uncommitted, local changes (this check is currently implemented)
2) local commits that are not pushed to the remote yet (this is not implemented yet)
Openshift server adapter: on first push it says that it has no local
changes. Even though local clone has 1 commit more than remote
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13175
URL:
https://issues.jboss.org/browse/JBIDE-13175
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.0.0.Beta2
Reporter: Andre Dietisheim
Assignee: Burr Sutter
Fix For: 4.1.x
Attachments: 1-local-change.png, no-local-changes.png, no_changes_yes.png
# EXEC: launch *OpenShift Application* wizard and create a new application / import
existing one
# ASSERT: you get the OpenShift application imported to your workspace
# EXEC: in *Servers* view, select the adapter for your OpenShift application and pick
*Publish* from its context menu
Result:
The adapter tells you that there are no local changes. If you look at your local project
you'll see in the git-decoration that the local git repo is ahead of 1 commit of the
remote, so there is a local commit that could be pushed/published.
!no-local-changes.png!
Expected result:
The adapter should tell you that there are local changes and ask you if you want to
publish them.
--
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