Rovo Dev keeps creating new PRs to add a .rovodev/.review-agent.md

[mispr]

For every PR I that I open in a repository, Rovo Dev creates a second PR to add a .rovodev/.review-agent.md. I don't want these files, and I don't want these PRs. I can't find any toggle to turn this behaviour off and Rovo wasn't even able to correctly identify the behaviour.

How can I prevent this behaviour, while still allowing Rovo Dev to review the PRs I create?

[Arkadiusz Wroblewski]

Hello and welcome to the Community @mispr 

I would recommend checking your Repository and Workspace settings for Rovo Dev first. You should also look at any Jira automation rules using the “Generate code” action or your Bitbucket Pipelines configuration to see if they’re triggering the agent. It’s also possible a template or onboarding rule is automatically generating that review-agent file.

For the reviews themselves, the primary setting to verify is the trigger frequency in the repository settings, this controls whether reviews happen on PR creation, on every commit, or not at all. Focus on these areas before troubleshooting individual code generation blocks, as the trigger logic is usually managed at the repository or organization level. 

[mispr]

Repository and Workspace settings were the first things that I checked, there isn't anything there to configurate this behaviour. Our pipelines also don't have anything that relates to this. I just check automation in Jira, it's not set up to do this.

To be clear: these repos have all existed for a very long time, and Rovo Dev PR reviews has been turned on for a while now, this has just started happening recently.

I had also asked Rovo Dev about this behaviour, and they didn't think it was manageable anywhere. :/ 

[Arkadiusz Wroblewski]

@mispr 

Well that's actually problem with generatives AI, managing behavior are still.... Meh.