Partly inspired from thinking about T297880: Improve documentation for GrowthExperiments, I think it could be helpful to have a git commit message template for GrowthExperiments. Here's an example git commit template https://gist.github.com/lisawolderiksen/a7b99d94c92c6671181611be1641c733
Looking at that user's template, we could perhaps modify it to have prompts to encourage updating documentation, and writing tests.
# Title: Summary, imperative, start upper case, don't end with a period
# No more than 50 chars. #### 50 chars is here: #
# Remember blank line between title and body.
# Body: Explain *what* and *why* (not *how*)
# Wrap at 72 chars. ################################## which is here: #
# Does your patch require updating documentation in ./docs? If so please update
# the docs!
# Does your patch have tests?
# Bug: {Phab}
# At the end: Include Co-authored-by for all contributors.
# Include at least one empty line before it. Format:
# Co-authored-by: name <user@users.noreply.github.com>
#
# How to Write a Git Commit Message:
# https://chris.beams.io/posts/git-commit/
#
# 1.Separate subject from body with a blank line
# 2. Limit the subject line to 50 characters
# 3. Capitalize the subject line
# 4. Do not end the subject line with a period
# 5. Use the imperative mood in the subject line
# 6. Wrap the body at 72 characters
# 7. Use the body to explain what and why vs. how