You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
git who table -l
┌──────────────────────────────────────────────────────────────────────────────┐
│Author Last Edit Commits Files Lines (+/-)│
├──────────────────────────────────────────────────────────────────────────────┤
│Bobby Foo 3 weeks ago 316 228 17,168 / 3,171│
│Foo, Bobby 3 weeks ago 301 109 11,487 / 3,946│
│Tom the Horse 3 weeks ago 103 156 7,788 / 7,633│
│the Horse, Tom 2 weeks ago 22 74 6,806 / 3,918│
│...8 more... │
└──────────────────────────────────────────────────────────────────────────────┘
As you can see, we have 2 users which show up twice each. The somewhat weird reason is, that we authenticate to Gitlab using LDAP, which sometimes reports us as prename name and sometimes as name, prename.
I'd like to have an option in git-who to merge these kind of users to get summary stats of the whole user.
For instance:
git who table -l -mergeuser "Bobby Foo+Foo, Bobby"
┌──────────────────────────────────────────────────────────────────────────────┐
│Author Last Edit Commits Files Lines (+/-)│
├──────────────────────────────────────────────────────────────────────────────┤
│Bobby Foo 3 weeks ago 617 337 28,655 / 6,117│
│Tom the Horse 3 weeks ago 103 156 7,788 / 7,633│
│the Horse, Tom 2 weeks ago 22 74 6,806 / 3,918│
│...8 more... │
└──────────────────────────────────────────────────────────────────────────────┘
Would be really great!
The text was updated successfully, but these errors were encountered:
I have the following situation:
As you can see, we have 2 users which show up twice each. The somewhat weird reason is, that we authenticate to Gitlab using LDAP, which sometimes reports us as
prename name
and sometimes asname, prename
.I'd like to have an option in
git-who
to merge these kind of users to get summary stats of the whole user.For instance:
Would be really great!
The text was updated successfully, but these errors were encountered: