Currently, the tool assumes the configurations (roles, channels) are at the root level of the yaml. It would be useful if there was an optional field to direct it at a field in the yaml where those configurations are, so that the yaml can have a different structure (e.g if it serves other purposes as well).
I don't know if this is best practice, and it seems a bit weird to have such "pointers" to other locations in the YAML file. I think it's more than reasonable to just have a separate config for auto_guild.
Currently, the tool assumes the configurations (roles, channels) are at the root level of the yaml. It would be useful if there was an optional field to direct it at a field in the yaml where those configurations are, so that the yaml can have a different structure (e.g if it serves other purposes as well).