Consider customizable strategy to get commits within graph builder

[mkondratek]

Some workflows and styles cause a huge amount of commits making graph table content very high and hard to read. :disappointed:

Consider adding some support to define a limitation of commits printed per branch. It can depend on:

• plugin settings #270 :rocket:
• machete file (possibly different limits for different branches but possibly very redundant too) :scroll:
• registry (seems to be a good and simple solution since this option will not be changed often) :registered:

Note that some hiding commits indicator shall be provided.

[PawelLipski]

As a visualization:

(not reproducible on my machine in the plugin currently since fork point overrides aren't handled yet)

[PawelLipski]

In other projects, I typically dealt with that by removing master from .git/machete, and only reverting it around develop->master releases ;D

[radeusgd]

As @mkondratek was asking for feedback - I like to have listing commits enabled, as it enables a nice overview of the changes in my branch and is especially useful to remember which commits came from which branch once I'm rebasing after a squash-merge of a PR has happened. But due to squashing of PRs, we are usually creating lots of small commits as part of a pending PR, which causes the tree to grow - then I need to expand the Machete window almost to full-screen to see all my branches or disable listing commits for a while if I want to operate on them. I think I would appreciate a way to configure not displaying all of the commits in a branch but just some of them. What I think would be great is to still be able to see both a few of 'first' and 'last' commits from a given branch, i.e. for a branch with commits A through Z, something along the lines of:

develop
|  A
|  B
| (... and 22 hidden commits)
|  Y
|  Z
| - my-branch

would be really cool :)

Edit: just to illustrate, a screenshot from just now where I need to expand to fullscreen or hide commits: we just do a lot of small commits :)

[mkondratek]

Thank you for the specific feedback here!

I use the commits view very rarely; I don't know what your preferences are on this @PawelLipski. Anyway, I think that we could treat this now as externally-requested and give it a higher priority.

Thank you, @radeusgd for the suggestion of how to resolve this one - it's almost the same conclusion we came to discussing this issue yesterday with Paweł.

[PawelLipski]

+1, let's include that in one of the incoming releases indeed :)