local branch more verbose

[Antonio D'Mora]

Hi,

Before I started using git-cola i was using smartgit-hg and I think that tool is a powerful one, with the con of being a privative software, and I'm use to a little widget wich lists all the branches existing in your repo. here is a snapshot:

this is a convinient tool for noobies at git, so you can know how many branches there are, what branch you are standing at, what branches are created on your local repo and your remote(s). Also It include a list of tags, also very usefull.

I'd like to addres this issue too, but I have no Idea of wich approach to use for this...

Regards,

Antonio.

[David Aguilar]

On Wed, Apr 22, 2015 at 12:23:57PM -0700, Antonio D'Mora wrote:
> Hi,
>
> Before I started using git-cola i was using smartgit-hg and I think that tool
> is a powerful one, with the con of being a privative software, and I'm use to a
> little widget wich lists all the branches existing in your repo. here is a
> snapshot:
>
>

> [Captura]

>
> this is a convinient tool for noobies at git, so you can know how many branches
> there are, what branch you are standing at, what branches are created on your
> local repo and your remote(s). Also It include a list of tags, also very
> usefull.
> I'd like to addres this issue too, but I have no Idea of wich approach to use
> for this...
>
> Regards,
>
> Antonio.

This reminds me of Paul H's sug:

https://github.com/git-cola/git-cola/issues/415

A dedicated "branch/tag navigator" tool could be pretty useful.

If you're looking for ideas on how to get started on something
like that, I'd recommend starting with simple mockups first to
sketch out the desired interactions and usability aspects.

The important aspects seem to be being able to concisely show
branches, tags, a summary of the commits at their tips, their
dates.

In addition to being able to see them (maybe in some kind of
table), we also probably want to be able to select one at a time
and checkout, rebase, and create new branches/tags at that
point.

There's probably be a fair amount of overlap between what we'd
want to do in this new tool and what can currently be done in
the existing `git dag` tool.

One idea would be to leverage `git dag` tool and implement this
new tool as a panel within `git dag`. This can help limit its
scope and keep it simple.

For example, I can imagine that selecting a branch in the
Navigator tool would select the corresponding commit in the
dag's widget. This would make it really easy to jump around
branches without needing to click around in the history view to
find the tips of each branch.

It would also leverage all of the existing features so that the
new tool doesn't need to implement all of them. All it'd need
to implement would be the branch/tag sha-1 selection signals.
--
David