[X] I have checked there are no open requests referencing the same feature
Description
It would be helpful if we could have settings across multiple locations. For instance, I would put global settings in the ~/.config/sourcery/sourcery.yaml file. Then within a project have different (as is more fine-tune, or overwrite existing) settings.
For instance, the rule_settings > python_version would be globally to the system version of python. But with virtual environments, that value may or may not be correct.
I would also turn the coding_assistant off by default (some projects forbid generative AI) and only enable it in projects that would allow such things.
Currently, once the ~/.config/sourcery/sourcery.yaml file is read, it does not read the .sourcery.yaml from the top-level of a project so there is no way to have multiple configurations.
Checklist
Description
It would be helpful if we could have settings across multiple locations. For instance, I would put global settings in the ~/.config/sourcery/sourcery.yaml file. Then within a project have different (as is more fine-tune, or overwrite existing) settings.
For instance, the
rule_settings > python_versionwould be globally to the system version of python. But with virtual environments, that value may or may not be correct.I would also turn the
coding_assistantoff by default (some projects forbid generative AI) and only enable it in projects that would allow such things.Currently, once the
~/.config/sourcery/sourcery.yamlfile is read, it does not read the.sourcery.yamlfrom the top-level of a project so there is no way to have multiple configurations.