Automation rules: allow defining them via .readthedocs.yaml file

[Daltz333]

It would be incredibly beneficial if automation rules could be specified via the readthedocs config file.

My team uses a single repository for documentation, and a separate repository that hosts a completely automatic sync of translations from transifex. A new language is added to transifex and it'll automatically sync to GitHub.

This repository is here.

Through our documentation release process, we tag docs at the beginning of each year. Ideally, we'd like to have this automatically populate through the several readthedocs projects we have without additional effort on the dashboard side.

Examples of the projects we have are:

• frc-docs (main)
• frc-docs-es
• frc-docs-fr
• frc-docs-he
• frc-docs-pt
• frc-docs-tr
• frc-docs-zh_CN

Currently, we have to set up an automation rule for each new language added. This gets cumbersome for every new language added.

[stsewd]

Hi, we have discussed this before, and everything comes to one decision: "should we have global options in the configuration file?"

Currently, we only have per-version options in the config file. We have also discussed to maybe have something like a bot/github action that makes use of our API instead (we don't have an API endpoint for automation rules yet #7350).