forked from redhat-appstudio/infra-deployments
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.pr_agent.toml
More file actions
36 lines (30 loc) · 1.35 KB
/
Copy path.pr_agent.toml
File metadata and controls
36 lines (30 loc) · 1.35 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
[github_app]
# persistent PR reviews
handle_push_trigger = true
push_commands = [
"/agentic_review"
]
# Removes internal Jira links
require_ticket_analysis_review = false
[pr_reviewer]
extra_instructions="""\
This is a GitOps monorepo deploying Kubernetes components across multiple clusters.
RING DEPLOYMENT PATTERN — Do NOT flag as a bug or incomplete change:
- Production changes are intentionally split across multiple PRs (ring1, ring2, ring3),
each targeting different cluster directories under components/<name>/production/<cluster>/.
- It is correct for a PR to only modify a subset of production cluster directories.
- Do NOT suggest applying changes to additional clusters beyond those in the PR.
PROMOTION ORDER:
- Changes flow: development → staging → production.
- It is expected that a change lands in dev/staging first, then production in rings.
- A production PR without a matching dev/staging change is intentional if dev/staging
was already merged in a prior PR.
Focus review on: YAML/Kustomize correctness, consistency within THIS PR's scope,
security concerns, and reasonable resource/image specs.
"""
[pr_code_suggestions]
extra_instructions="""\
Do not suggest applying production changes to additional cluster directories
beyond those in the PR. This repo uses ring deployments — clusters are updated
in separate PRs intentionally.
"""