Bugzilla – Full Text Bug Listing
| Summary: | Hierarchical layout for tags in Git Repositories view | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Stephan Herrmann <stephan.herrmann> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | chandrayya.gk, marco, markus.kell.r, niks, robin |
| Version: | 2.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Stephan Herrmann
I assume you mean in the Git Repositories view? Tags are usually versions or dates. Could you give an example how they could be shown in a hierarchical layout? Do you have an example use case? (In reply to comment #1) > I assume you mean in the Git Repositories view? Yea, sorry, should've said so. > Tags are usually versions or dates. Could you give an example how they could > be shown in a hierarchical layout? Do you have an example use case? Given that tags tend to accumulate to a very long list, back in the SVN days I got used to grouping them like: builds/ releases/ safety/ ... the builds/ folder hosts the long list of dates, I typically don't want to see, releases are more interesting, etc. So, e.g., today's build would be tagged with "builds/201209232000" Also: why not use per-committer tags like per-committer branches? Is it only me who does such grouping? +1 We also have these very long lists of tags that are grouped this way. A hierarchical layout for tags would improve the usability of the view. Yes. It's a very good feature. Also if we followed naming conventions for tags then we can filter these tags like resources in Package/Navigator view. See the question on SO http://stackoverflow.com/q/20348520/1391924 Shouldn't this be a low hanging fruit, given that the same already works for branches (via an option)? |