Persist user database #113
Description
PROPOSAL: Store a mailmap-aware user database in
~/.local/share/herostratus/cache/<repositories>/users.csv
The user database will be a CSV file with the following columns:
- email (mailmap resolved)
- name (mailmap resolved)
There will need to be a MailMapResolver that can combine mailmaps from the repo, mailmaps from the
Herostratus config, and possibly heuristic mailmaps to map users.noreply.github.com to real
emails. The user database should be generated by the RuleEngine (that is, it should not be
generated by the Rules themselves) as new commits are processed. It should be passed into
Rule::init_cache(), Rule::process(), and Rule::fini_cache() so that rules can access it after
they know all commits have been processed.
This is where #17 comes in.