[
https://issues.jboss.org/browse/JBIDE-17905?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-17905 at 7/17/14 5:58 AM:
-------------------------------------------------------------------
we agreed upon making the "Commit and Publish" button more intelligent and
allowing users to just push (not commit) if there are local changes that one can push. We
should then relabel "Commit and Publish" to "Publish" if no files are
checked for commit (but there's a local commit that we can push upstream).
I'll investigate how I can achieve this since the EGit commit dialog is not built with
extensibility in mind.
was (Author: adietish):
we agreed upon making the "Commit and Publish" button more intelligent and
allowing users to just push (not commit) if there are local changes that one can push. We
should then relabel "Commit and Publish" to "Publish" if no files are
checked for commit (but there's a local commit that we can push upstream)
Server Adapter: cannot publish commits when there are local changes
-------------------------------------------------------------------
Key: JBIDE-17905
URL:
https://issues.jboss.org/browse/JBIDE-17905
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Critical
Labels: respin-b, server_adapter
Fix For: 4.2.0.Beta3, 4.2.0.CR1
Add file test.txt
Commit test.txt
Add file temporary.txt
go to openshift server and push
Assert: I can push the new commits without having to do something about temporary.txt
this worked in past, now the new commit dialog prevents me from doing this.
I can use egit push to workaround this but that kinda defeats the purpose of making the
server interaction simple via just the "Publish" command.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)