Bugzilla – Full Text Bug Listing
| Summary: | Opening push dialog by 'Push...' should not automatically include configured push ref specs | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Edwin Kempin <edwin.kempin> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | robin |
| Version: | 0.12 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Edwin Kempin
I have configured a push specification, so that I can easily push to the configured destination by simply opening the context menu on the repository and choosing 'Push to upstream'. This push specification I use for 95% of my pushes. However from time to time I want to do a different push (e.g. I want to push a certain tag, or I want to push to the Gerrit sandbox of another user, etc.). In this case I need to open the push dialog and explicitly specify the push ref specification. That's fine and I do it by choosing 'Push...' from the context menu on the repository. However what I find annoying is that in this case the push dialog already contains the pre-configured push ref specs and I explicitly have to delete them if I don't want to push to them right now. My use case is like this, if I want to push to my pre-configured push ref specs I use 'Push to upstream', if I use 'Push...' I always want to push with some ref spec which is different than the predefined ones. This is why I think that the configured push ref specs should not automatically be included if the push dialog is opened by 'Push...'. What do you think? Looks like this has been fixed in the meantime, closing. |