.pr_agent.toml

[config]
add_repo_metadata = true

[pr_code_suggestions]
extra_instructions = """\
- Before suggesting package version constraints, verify compatibility information from official documentation
- For .NET NuGet packages, check the official NuGet.org package page for accurate compatibility information
- Do not suggest version constraints based on assumptions about framework compatibility
- Check PR checks before suggesting changes that you think will fix compilation errors. If the checks pass, it means that there are no compilation errors, and no suggestions are required (missing imports, using statements, etc).
- The project uses C# 14 features. Do not suggest fixes for "invalid syntax", such issues will be exposed by the CI checks.
- The latest GA version of .NET is 10. Do not suggest removing the net10.0 target because it's preview. It's not.
- Always use the latest C# version (14 at the moment).
- Before suggesting to remove a variable, verify it's not used anywhere in the visible code context
- Do not suggest removing variables that are clearly used in subsequent lines
For C#:
- Do NOT assume `where T : struct` permits `Nullable<T>` (`int?`, etc.). The compiler rejects `T = Nullable<U>` under this constraint (CS0453).
- Before flagging a bug involving generic constraints, explicitly verify (in the explanation) whether the code can compile and the call site is legal.
- If the scenario requires `T = int?` through a `where T : struct` API, treat it as invalid/unreachable unless there is evidence of a different overload or non-generic path.
"""

[rag_arguments]
enable_rag=true

[pr_description]
auto_create_ticket = true

[pr_compliance]
extra_instructions = """\
- There's no need to enforce audit logs compliance as it's a framework. Extensive diagnostics is useful, but we don't need audit logs.
- When in doubt about null checks, make sure that the property or field is indeed nullable. Rely on compiler warnings in build results for questionable null check practices.
"""