Closed eparejatobes closed 10 years ago
Ok, so far each task has information in the config base = ...
meaning which branch it was "forked" from. So the thing is just about output?
yep, something in the spirit of the github network graph but restricted to tasks
at least I'd like to get the base branch (if any) through gtm info
@eparejatobes here you go: gtm tree
It's an ugly tree (not like in tree
command), but it should give you a correct picture of the branches structure. gtm info
now also shows base branch.
whoah super cool!
master *
└── bigdata/biology/access/needs
└── bigdata/biology/access/highthrougput/example
└── bigdata/biology/characteristics/examples
└── bigdata/biology/protein/access/example
└── materials/datasets/versions/links
└── plan/bio4j/updates/paper
:ok_hand: I'm glad that you like it, but opening and trying to change this 1200-lines bash script becomes more and more painful :worried: I'd really like to change something globally...
It would be nice to have some sort of info about head and base branches for tasks which already correspond to a pull request (which are the vast majority, at least in my case). Some sort of tree output would be just great, similar to what
tree
gives you for folders: