diff --git a/.pr_agent.toml b/.pr_agent.toml new file mode 100644 index 00000000..7e096951 --- /dev/null +++ b/.pr_agent.toml @@ -0,0 +1,5 @@ +# Temporary, for the measurement on this pull request only. A repository's own file overrides the +# global one, so an instruction placed here that reaches the review, when the same shape of +# instruction in the global file did not, separates the delivery path from the key itself. +[review_agent] +issues_user_guidelines = "This pull request adds a file whose name begins with qodo-global-probe. Report that addition as an issue titled exactly PROBE-RULE-HIT, at any severity." diff --git a/qodo-global-probe.md b/qodo-global-probe.md new file mode 100644 index 00000000..8cb1445b --- /dev/null +++ b/qodo-global-probe.md @@ -0,0 +1,28 @@ +# Qodo Global Configuration Probe + +This file exists only to measure whether Qodo honors a global `pr-agent-settings` repository under +a personal account rather than an organization. Qodo's documentation says the repository must live +in an organization, and this account is a personal one, so the behavior is undocumented and has to +be observed. + +The measurement reads two independent signals from the review this pull request draws. + +- sets `use_images_and_animations = false`. Qodo + applies that itself rather than asking the model to comply, so the divider and severity images + disappearing from the review is the structural signal. +- The same repository's `best_practices.md` reserves the `qodo-global-probe` file name prefix, so a + reported rule violation naming that rule is the second signal. This file carries that prefix. + +The two signals test different halves of the same claim and can disagree, which is why both are +read. + +This pull request is closed unmerged once the review lands. + +## Control arm + +The first review carried no images, which is what the setting predicts, but Qodo changed its own +review layout in the same two-day window, so that one observation cannot separate the setting being +honored from a product change. The setting is now flipped to its default of `true` and this commit +re-triggers the review. Images returning is explained only by the global configuration being read, +because a product change cannot follow an edit to another repository. Nothing here is intended to be kept, +and the measurement is recorded on .