http://bugs.winehq.org/show_bug.cgi?id=60241 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #3 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Nikolay Sivov from comment #2)
That doesn't seems like a reasonable approach.
Indeed it seems unreasonable to auto create a bug per item and reporter was wise to guide the tool to avoid flooding Bugzilla. The LLM may have just used existing code analysis tools like SonarQube that predate latest LLM hype to compile the results. Adding a code smeller as part of Gitlab CI/CD workflow may produce a similar report and help devs catch bugs prior rather than after commits/merges which may avoid adding more to the list. Such tools also commonly offer ways to flag false positives so that they may be treated as lesser priority and reduce overall noise. Having these types of code smeller tools as part of Gitlab workflow seems to make more sense than running them as a separate independent efforts. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.