From 3576455960ee88cefa43cad0bdfd1458549569b9 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Fri, 30 Jan 2026 20:25:26 +0100 Subject: pkg/aflow/flow/patching: use recent commit subjects Give LLM the recent commit subjects when it generates description, so that it can use the same style. Add infrastrcuture to write end-to-end action tests to test it. --- pkg/aflow/flow/patching/patching.go | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'pkg/aflow/flow/patching/patching.go') diff --git a/pkg/aflow/flow/patching/patching.go b/pkg/aflow/flow/patching/patching.go index 1906204ec..f8ee75a31 100644 --- a/pkg/aflow/flow/patching/patching.go +++ b/pkg/aflow/flow/patching/patching.go @@ -75,6 +75,7 @@ func createPatchingFlow(name string, summaryWindow int) *aflow.Flow { MaxIterations: 10, }, getMaintainers, + getRecentCommits, &aflow.LLMAgent{ Name: "description-generator", Model: aflow.BestExpensiveModel, @@ -222,6 +223,12 @@ Additional description of the patch: {{.PatchExplanation}} +Here are summaries of recent commits that touched the same files. +Format the summary line consistently with these, look how prefixes +are specified, letter capitalization, style, etc. + +{{.RecentCommits}} + {{if titleIsWarning .BugTitle}} If the patch removes the WARN_ON macro, refer to the fact that WARN_ON must not be used for conditions that can legitimately happen, and that pr_err -- cgit mrf-deployment