Bugzilla – Full Text Bug Listing
| Summary: | Branches should be organised by remote, rather than local/remote | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Alex Blewitt <alex.blewitt> |
| Component: | Core | Assignee: | Mathias Kinzler <mathias.kinzler> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | mathias.kinzler, stefan.lay |
| Version: | unspecified | ||
| Target Milestone: | 1.0.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Good idea. I've started to work in this, will take some time, though. Code review at http://egit.eclipse.org/r/#change,1467 Merged as e42e2d61222fbb90078e7b3b9a52e5c2fe892801 |
Build Identifier: In the Git Repositories view, the Branches tree is split into Local Branches and Remote Branches, which mirrors the layout on disk for the git repository. However, I think it would be a good idea to permit them to be categorised by remote name; for example, consider a config with three remotes (eclipse.org, github.com, and internal.com). At present, it looks like: + Branches + Local Branches master + Remote Branches eclipse.org/master eclipse.org/stable-0.7 eclipse.org/stable-0.8 github.com/master github.com/stable-0.8 internal.com/master However, I think it would look more useful as: + Branches + Local master + eclipse.org master stable-0.7 stable-0.8 + github.com master stable-0.8 + internal.com master Reproducible: Always