feat: automatically generate .sauced.yaml file

[zeucapua]

Description

Two modes of generating:

• Automatic

  • Each found email will be attributed to the given Git name

• Interactive

  • Each found email will prompt the user to set the name it should be attributed to
  • The attribution name can be different from the email's Git name
  • Multiple emails can be attributed to one user
  • Can ignore an email with Ctrl+I

Related Tickets & Documents

Closes #97

Mobile & Desktop Screenshots/Recordings

Steps to QA

1. Run just build
2. Run ./build/pizza generate config
3. Use the -o/--output-path flag to set a directory
4. Use the -i/--interactive flag to attribute each email manually

Tier (staff will fill in)

• Tier 1
• Tier 2
• Tier 3
• Tier 4

[optional] What gif best describes this PR or how it makes you feel?

[jpmcb]

PSA: you'll want to rebase on beta to get the latest linter config from #148

[jpmcb]

Great stuff! Just a few small nits and this is ready to go! Seriously, huge lift. Great work 🐹

[nickytonline]

Having an existing .sauced.yaml, it regenerated it, but the missing premable in comments got removed. Not sure if that's from our template, but just mentioning it.

When regenerating the .sauced.yaml, if one is detected (non-interactive mode) potentially mention it before they proceed.

Also, not sure how far back we're looking by default in the git history, but I see Anush, one of our interns in the list.

Also, we should skip known bot accounts, i.e. any account ending in [bot].

[nickytonline]

This is working really great @zeucapua! Small change request.

[nickytonline]

🚢

[zeucapua]

Having an existing .sauced.yaml, it regenerated it, but the missing premable in comments got removed. Not sure if that's from our template, but just mentioning it.

When regenerating the .sauced.yaml, if one is detected (non-interactive mode) potentially mention it before they proceed.

Also, not sure how far back we're looking by default in the git history, but I see Anush, one of our interns in the list.

Also, we should skip known bot accounts, i.e. any account ending in [bot].

These can be in a future PR:

• Warn of existence/use existing .sauced.yaml config
• Add a --range to how far to check commit logs
• Add a preamble eg pizza generate codeowners on the .sauced.yaml file!
• Ignore [bot] contributors

Should I make issues?

[jpmcb]

Should I make issues?

Yes, I was going to say: let's followup any additional feedback / bugs in new issues and PRs