GitHub Actions API/UI：查询结果超2500条时显示“2,500+”而非精确计数
Changes to query results in the GitHub Actions API and UI
自动化运维与 CI/CD 监控重度用户注意：API 返回的总记录数上限逻辑已变，依赖精确计数的脚本需立即适配，建议增加时间范围过滤以规避此限制。
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.
在 GitHub Actions API 和 UI 中，按工作流、事件、状态、分支或参与者搜索时，对工作流运行的查询现在返回的计数精度较低但更准确。我们将继续返回最多 1,000 项的分页结果。但是，如果找到的记录数超过 2,500，我们将报告“2,500+”，而不是尝试返回确切的数量。这是因为检索超过 2,500 条记录的查询经常超时，并返回超时前找到的记录数，而不是真实数量。通过实施此限制，我们的计数将更加准确，并且我们将提高客户的性能。
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.
如果您的集成或脚本依赖于从单个查询中检索超过 2,500 个匹配的工作流运行，请缩小您的筛选条件（例如，通过添加日期范围）以检索您需要的特定运行。此更改正在 github.com 和 GitHub Enterprise Cloud 上逐步推出。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力