Storia in 2 fonti

Code Quality findings now have a REST API a pipeline can actually call

GitHub put its Code Quality CodeQL findings behind two read-only REST endpoints in public preview, one for listing with filtering and pagination, one for a single finding. The change turns the Code Quality UI's data into something CI/CD jobs and remediation tooling can finally consume on their own schedule.

Raccontata da

github.blog

dev.to

Confronto fonti

2 prospettive sulla stessa storia

AI · summaries

dev.toStai leggendo13 g fa

Code Quality findings now have a REST API a pipeline can actually call

originale

github.blog13 g fa

Fetch Code Quality findings via REST API - GitHub Changelog

Repository-level REST APIs for Code Quality findings are now available in public preview, bringing API support closer to the functionality already available in the GitHub UI. Two new read-only endpoints…

Leggi questa versione → originale

Code Quality findings now have a REST API a pipeline can actually call

Fetch Code Quality findings via REST API - GitHub Changelog

Timeline cronologica

Fetch Code Quality findings via REST API - GitHub Changelog

Code Quality findings now have a REST API a pipeline can actually call