What's the recommended approach for sharing the pr_agent.toml file with multiple Repos?

[LawrenceMantin]

Our company has many Azure DevOps repos that I would like to use the same pr_agent.toml file to maintain consistency and reduce redundancy. What's the recommended approach, and are there any examples of azure-pipeline to make this work? Thanks.

[gaeljw]

Interested in this as well, in a GitLab CI webhook context.

I was considering the easiest might be a dedicated instance of PR-agent per group of configurations with configurations set at the instance level rather than in repositories. This might not be affordable to everyone though and has it's own challenges.

Ideally, there could be some kind of inheritance in a similar manner to how RenovateBot does it: each config file in a repo can reference another repo and automatically includes its configurations.

---

Another approach, if you running PR agent through a CI pipeline is to set the config in the pipeline rather than in config file and I guess you can have some kind of "includes" to import a shared job definition in Azure DevOps? This is a guess, I don't know Azure but this is something that would be doable in GitLab CI.

[steve-orbussoftware]

If a repo is created using the recommended naming (pr-agent-settings) and a .pr_agent.toml file is located within it, why can't the qodo agent pull that config from that repo? Provided the PAT has sufficient permissions to read that repo of course.

Is there a blocking problem or it's just not implemented, @mrT23 ?