Changes to query results in the GitHub Actions API and UI
Workflow run queries in the GitHub Actions API and UI now return a less precise but more accurate count of records when searching by workflow, event, status, or branch.
Queries for workflow runs in the GitHub Actions API and UI now return a less precise but more accurate count of records when you search by workflow, event, status, branch, or actor. We will continue to return paginated results of up to 1,000 items. However, if the number of found records exceeds 2,500, we will report “2,500+” instead of attempting to return the exact number of records. This is because queries that retrieve more than 2,500 records frequently timeout and return the number of records found before the timeout rather than the true count. By implementing this limit, our counts will be more accurate and we will improve performance for customers.
If your integrations or scripts rely on retrieving more than 2,500 matching workflow runs from a single query, narrow your filters (e.g., by adding a date range) to retrieve the specific runs you need. This change is rolling out now on github.com and GitHub Enterprise Cloud.
The post Changes to query results in the GitHub Actions API and UI appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Improved detection for withdrawn Dependabot alerts
Dependabot now provides improved detection for withdrawn alerts that are no longer valid due to advisory or vulnerability changes. This makes it easier to identify and manage alerts that have been removed.
Search and filter for budgets now available
The Budgets and alerts page in GitHub billing settings now displays all budgets in a single searchable and filterable list, making it easier to manage multiple budgets.
Code scanning AI Scan metrics in security overview
Organization and enterprise administrators can now view metrics showing AI Scan findings generated and resolved in the security overview dashboard, providing visibility into the impact of AI-powered code scanning on pull requests.