If the Branches & tags field of gitk view is populated then stash ends up filtered out. If stash is added to the list it shows, but then an error ends up happening if there is no stash. These behaviors are literally correct so certainly shouldn't be changed, but they're potentially confusing and unlikely to be what the user actually wants. Perhaps adding a Stash checkbox to the list of checkboxes would be worthwhile? It would actually mean 'Stash (if present)' but I think it would be clear enough. IMO it would then be good to have it checked by default in new views. A similar consideration applies when there's an ongoing interactive rebase: it's unfortunate that the commits and staged and unstaged changes on the in-progress rebase end up filtered out. They can be explicitly added back in by adding 'git rev-list --ignore-missing REBASE_HEAD..HEAD' to the 'Command to generate more commits to include:' field, but it might be nice if there was a more obvious way to achieve this. It's less obvious here what it might be though. The general thing here is that it would be nice if branch views had an obvious way to show the stuff that users probably want to see when working on branches. I'm definitely not in favor of outright cheating and making filter options not really do what they say (keeping interface and interface close is more important than usability in context of git IMO) but if there was some box to check to "show all that stuff" and it was reasonably clear what the stuff was I'd be happy to click it :) Britton
