ci: add qodo review config

[smith-xyz]

Adding qodo config for ai assisted reviews

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smith-xyz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [smith-xyz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[smith-xyz]

/config

[smith-xyz]

/agentic_review

[smith-xyz]

/hold

waiting to see why this wasn't triggered

[smith-xyz]

/agentic_review

[qodo-for-rh-openshift]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Push-triggered review churn ✓ Resolved 🐞 Bug ➹ Performance

Description

handle_push_trigger = true with push_commands = ["/agentic_review"] will cause the agent to
re-run on every push to a PR branch. This can create repeated comment updates and unnecessary
compute/API usage (amplified by persistent_comment = true).

Code

.pr_agent.toml[R1-5]

+[github_app]
+feedback_or_draft_pr = false
+handle_push_trigger = true
+pr_commands = ["/agentic_review"]
+push_commands = ["/agentic_review"]

Evidence

The config explicitly enables push triggers and assigns /agentic_review to run on push events; the
same file enables persistent comments which increases PR comment churn from repeated executions.

.pr_agent.toml[1-5]
.pr_agent.toml[20-28]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PR agent is configured to run `/agentic_review` on *push* events (`handle_push_trigger=true` + `push_commands=["/agentic_review"]`). This will re-trigger reviews on every pushed commit, which is typically noisy and can consume extra API/compute.

## Issue Context
The same config also enables `persistent_comment = true`, which means repeated runs are likely to keep updating the PR’s persistent summary comment.

## Fix Focus Areas
- .pr_agent.toml[1-5]
- .pr_agent.toml[20-28]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Undocumented agent config ✓ Resolved 🐞 Bug ⚙ Maintainability

Description

The repo documents Prow-based CI but does not document how/when this new PR-agent GitHub-app
configuration is expected to be used. This makes the config easy to misinterpret or become stale
because its operational owner and trigger model aren’t captured in-repo.

Code

.pr_agent.toml[R1-37]

+[github_app]
+feedback_or_draft_pr = false
+handle_push_trigger = true
+pr_commands = ["/agentic_review"]
+push_commands = ["/agentic_review"]
+
+[auto_best_practices]
+enable_auto_best_practices = true
+utilize_auto_best_practices = true
+
+[checks]
+enable_auto_checks_feedback = false
+
+[config]
+publish_output_progress = false
+
+[pr_code_suggestions]
+enable_chat_in_code_suggestions = true
+
+[review_agent]
+enabled = true
+approve_pr_on_self_review = false
+comments_location_policy = "summary"
+demand_self_review = true
+final_update_message = false
+persistent_comment = true
+persistent_comment_notification = false
+publish_output = true
+
+[review_agent_ux]
+finding_overflow_count = "all"
+expand_description = true
+expand_code = false
+expand_relevance = false
+expand_evidence = false
+expand_prompt = true
+resolved_overflow_count = "none"

Evidence

AGENTS.md describes CI being run via Prow/openshift-release config, while the PR introduces a
GitHub-app agent config file without any corresponding mention in that CI documentation.

AGENTS.md[37-40]
.pr_agent.toml[1-37]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A GitHub-app config file (`.pr_agent.toml`) was added, but there is no in-repo documentation describing its intended usage, ownership, or how it fits alongside the repo’s existing CI (documented as Prow-based).

## Issue Context
Without documentation, maintainers may not know whether this file is expected to be active in this repo, what triggers are intended (PR comment vs push), or how to change it safely.

## Fix Focus Areas
- AGENTS.md[37-40]
- .pr_agent.toml[1-37]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[smith-xyz]

/hold cancel

[openshift-ci]

@smith-xyz: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.