| Summary: | Always perform a dry run before "Push to Upstream" | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Markus Keller <markus.kell.r> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, deepakazad, remy.suen, stephan.herrmann |
| Version: | 1.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Keller
(In reply to comment #0) > I know I can use Team > Remote > Configure Push to Upstream... to get the > preview, but that's quite far away. I think that's not even true, see bug 363468. So this is really a bug. It must be possible to know what's going to happen on Push. Otherwise, horrible things like bug 361707 are more likely to happen. The preview is also important since Git has quite a steep learning curve, and especially new users cannot always tell what's going on behind the scenes (e.g. will Push push all branches or just the current one? Will it push tags?, etc.) +1 Are you suggesting this for all push operations or just "Push to Upstream"? Currently, I'd feel safest if such an option would apply to all pushes, no matter which workflow I used. It should apply to all operations that modify a remote repository. The Push... dialog already offers a dry-run if you click "Next >" on the "Push Ref Specification" page. The preference could enforce this by graying out the "Finish" button on that page (or by making "Next >" the default button). |