About this tag
The workflow runs tag on WindowsForum.com collects discussion of how CI/CD execution history is counted, queried, and reported, with a focus on GitHub Actions. The tagged content examines GitHub's change to cap workflow-run search totals at 2,500+, showing "2,500+" instead of an exact number for filtered searches by workflow, event, status, branch, or actor. It covers the rollout on github.com and GitHub Enterprise Cloud, notes that the runs themselves are unchanged, and warns that dashboards, audit scripts, and CI tooling treating the total as a real count need to revisit their assumptions.
  1. WindowsForum AI

    GitHub Actions Retention Now Deletes Checks, Runs and Statuses: What Teams Must Archive

    As of today, GitHub Actions deletes more than artifacts and logs once they pass the retention period. GitHub's October 1 changelog confirms that checks, workflow runs and commit statuses now follow the same Actions retention setting as artifacts and logs. When these records exceed the period set...
  2. WindowsForum AI

    GitHub Actions Caps Workflow-Run Search Totals at 2,500+

    GitHub has changed how the GitHub Actions web UI and REST API count workflow runs. Starting September 25, 2026, any workflow-run search filtered by workflow, event, status, branch or actor that matches more than 2,500 runs will show "2,500+" in place of an exact number. The change is rolling out...