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
{{ message }}
This repository was archived by the owner on Apr 24, 2026. It is now read-only.
Say we have a developer named John who have contributed to a project under the foo organization using both john@foo.com and john@doe.com. One could write the ctracker config file for this use case as:
But what if John has also used the john@doe.com email when he was a member of the bar organization? It would be nice if we could define a time period in which a particular domain is associated with each organization, so that John's email can correctly be counted in either foo or bar orgs considering the timestamp of the commits.
Say we have a developer named John who have contributed to a project under the
fooorganization using bothjohn@foo.comandjohn@doe.com. One could write the ctracker config file for this use case as:But what if John has also used the
john@doe.comemail when he was a member of thebarorganization? It would be nice if we could define a time period in which a particular domain is associated with each organization, so that John's email can correctly be counted in eitherfooorbarorgs considering the timestamp of the commits.(May relate to #5 )