Re: Full subsystem codebase scan for identifying pre-existing issues?

[Roman Gushchin <roman.gushchin@linux.dev>]

Joanne Koong <joannelkoong@gmail.com> writes:

> Hi Derek,
>
> On Wed, Jul 29, 2026 at 6:43 PM Derek Barbosa <debarbos@redhat.com> wrote:
>>
>> Hi,
>>
>> On Wed, Jul 29, 2026 at 01:34:10PM -0700, Joanne Koong wrote:
>> > Hi,
>> >
>> > Is there a way for Sashiko to run a full scan of a subsystem/tree to
>> > identify all the pre-existing issues so that they can be fixed
>> > proactively?
>>
>> At the moment, no. At least nothing that I am aware of :)
>>
>> There have been some small conversations about such functionality, but nothing
>> has really taken shape yet. One of the concerns was trying to validate the sheer
>> number of potential-false-positives, and how to present such information in an
>
> Gotcha, thanks for the context :) That makes sense, that sounds tough
> balancing potential false positives.
>
> Just thinking out loud here... if those false positives are currently
> getting reported/flagged by Sashiko on contributor submissions
> anyways, maybe it'd still be helpful for them to show up in the
> subsystem codebase scan so maintainers can course-correct the rules
> for them in Sashiko (and hopefully save contributors not as familiar
> with the subsystem some confusion :)).

This is in work too and I'm even somewhat optimistic that in many cases
Sashiko can generate these prompts automatically based on human
feedback. The tricky part is that human are often wrong too, so Sashiko
can't blindly trust human feedback either.