Open MaximilianHxrn opened 1 year ago
Automatic parsing of a git graph is a posteriori difficult because branch references are volatile and you don't have branches associated with each commits as in mercurial. So, to help git find back which commit belongs to which branch (or git-flow swimlanes), I would propose to have the users annotate some commits (because they know it best) and this info would be kept somewhere (in repo ?). Then a proper graph could be created; something along Plastic SCM view described in this discussion https://github.com/mhutchie/vscode-git-graph/issues/207
We use 90% of Git-Flow in our company (we dont use tags in some projects) which leads to the following problem:
My current understanding is, that every new commit is fitted as far left as possible and if needed is pushed one column to the right.
If we apply this logic to GitFlow it looks like this: Blue line: master Green line: develop Pink line: release/2 // 2 is an example name as i am not allowed to disclose the real branch name Purple line: release/1 Orange line: feature/1
I am open to suggestions on how to implement it and if neccessary I can contribute with my non-existent TS-skills