Bugzilla – Full Text Bug Listing
| Summary: | Configuring a push ref specification for 'tags/myTag' proposes 'tags/myTag' as destination ref which results in push to 'refs/tags/tags/myTag' | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Edwin Kempin <edwin.kempin> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | matthias.sohn |
| Version: | 0.12 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
Fix proposed at http://egit.eclipse.org/r/#change,3836 merged as f22b04d49b43b0d1c06f59d17352ef04875b7cd0 |
Steps to reproduce: 1. create a tag 'refs/tags/myTag' 2. open the push dialog and enter 'tags/myTag' as source ref 3. press tab to set focus onto the destination ref input field 4. the destination ref is automatically set to 'tags/myTag' 5. add this push ref specification ('tags/myTag:tags/myTag') 6. push and see that the push is done to 'refs/tags/tags/myTag' What is expected? It is expected that either the push would be done to 'refs/tags/myTag' or that the proposed value for the destination ref would be 'refs/tags/myTag' instead of 'tags/myTag'. Having 'refs/tags/myTag:refs/tags/myTag' as push ref specification works as expected.