review-classifier: say the 25-line context shows a gate only when it's within 25 lines
This commit is contained in:
parent
4098fd6d35
commit
276545fb45
2 changed files with 7 additions and 6 deletions
|
|
@ -289,9 +289,10 @@ lets the runtime's prompt cache reuse it across questions.
|
|||
|
||||
The controller builds the diff itself, from each changed file at the PR's
|
||||
merge base and at its head, with 25 lines of context around each change
|
||||
rather than the 3 of the forge's `.diff`. That keeps a moved block's
|
||||
enclosing gate in view, such as a `config = lib.mkIf …` or an option's
|
||||
`default`, so a move that restates the gate doesn't read as adding one. The
|
||||
rather than the 3 of the forge's `.diff`. An enclosing gate, such as a
|
||||
`config = lib.mkIf …` or an option's `default`, is in view when it is within
|
||||
25 lines of the change, so a move that restates it doesn't read as adding one.
|
||||
A gate further away is still out of view. The
|
||||
controller sends the forge's `.diff` instead when the PR changes more than
|
||||
100 files, when the forge names no merge base, when reading a changed file
|
||||
fails, or when the wide diff is over 256 KiB. The review then says so, with
|
||||
|
|
|
|||
Loading…
Reference in a new issue