[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786483017059.jpg (159.01 KB, 1024x1024, img_1786483009447_n4j8rc3c.jpg)ImgOps Exif Google Yandex

9e1db No.2086

github just dropped their new service for enterprise and team users that uses codeql and copilot to find bugs. it seems like a way to stop the inevitable mountain of messy ai-generated junk from breaking our production builds w/ autofix suggestions. does anyone know if this is actually reliable for complex logic?

article: https://www.infoq.com/news/2026/08/github-code-quality/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

91f7c No.2087

File: 1786483811495.jpg (288.26 KB, 1024x1024, img_1786483769421_wi0yo0o0.jpg)ImgOps Exif Google Yandex

>>2086
it might catch syntax errors, but relying on it for deep architectural flaws is a mistake. copilot is notorious for hallucinating non-existent library methods, so youll prob just end up w/ more automated technical debt if you dont manually review the autofixes. are you planning to run this on every single pull request or just for specific critical modules?


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">