search

hansu / vscode-git-graph

Fork of Michael Hutchisons repository with some updates.
Other
65 stars 9 forks source link

Fixed column IDs by branch name #26

Closed MaximilianHxrn closed 1 year ago

MaximilianHxrn commented 1 year ago

We use 90% of Git's GitFlow strategy to work in big repositories. image This is a filtered view of an example repository. Blue is our develop working branch and green our master. I would like to have a setting where i can put in a regex like. "\/master" and assign the row ID 1. then another for the develop "\/develop" and assign 3. in between i would assign "\/release\/.*" to ID = 2. So my repo always has master to the most left, release branches to merge develop into master in row 2 and our working branch on id 3.

The working branch which are merged into develop would be automatically placed on row 4 or higher and make my graph soooo much more readable for beginners in our company or rather our seniors trying to maintain the chaos.

Im open to implementing it myself if someone shows me the location of the code, that defines the row IDs of the graph. Im not an expert in Typescript but i have some time on my hand which Im willing to dedicate.

hansu commented 1 year ago

Because the license prohibits publishing on the marketplace I would suggest to put not too much work into this project. I suggest focusing instead on this project: https://github.com/phil294/git-log--graph/ (at least I will do so).

MaximilianHxrn commented 1 year ago

Thanks for the quick reply.

No offense to the author phil294 but the graph looks soooo much more worse than this graph here. My company is fine with the current git graph (not version 2) and we only need the feature i mentioned. Do you know the code a little (to point me in the right direction) ? Im also fine with doing the change on my own and using it internally at my company. Your extra features are nice to have but dont bring that much value for us

hansu commented 1 year ago

git-log--graph is still in an early development stage so the look will probably be improved.

Do you know the code a little (to point me in the right direction)?

Unfortunately the code is a bit of hard to understand, so I am sorry I can't help you out here.