Feature: comment preamble on generated .sauced.yaml configuration

[zeucapua]

Suggested solution

Add the following preamble before the data in the .sauced.yaml file:

# Configuration for attributing commits with emails to GitHub user profiles
# Used during codeowners generation.

# List the emails associated with the given username
# The commits associated with these emails will be attributed to
# the username in this yaml map. Any number of emails may be listed

Context

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].

Originally posted by @nickytonline in #137 (review)

[open-sauced]

🎉 This issue has been resolved in version 2.2.0-beta.4 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[open-sauced]

🎉 This issue has been resolved in version 2.3.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[open-sauced]

🎉 This issue has been resolved in version 2.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀