fleet-cleaning-ci

To clean up orphaned GitHub Actions workflow YAML files, you can inventory a repository or fleet to identify legacy files and safely remove them using gated actions. This ensures only superseded workflow configurations are deleted.

You can disable Dependabot automated security fixes via the GitHub API to stop automated PRs while retaining vulnerability alerts. This adjustment is applied during the CI cleanup sweep across the fleet.

Purging stale workflow run history involves deleting outdated workflow run records via the GitHub API. A read-only inventory identifies stale runs, and gated actions execute the deletions to reflect the current CI shape.

Yes, you need repository CI configuration access and GitHub API permissions to perform deletions and updates. The cleanup process uses a read-only inventory phase first, then requires elevated permissions to apply the proposed changes.

Yes, you can run a read-only inventory to identify orphan CI files, disabled Dependabot security, and stale workflow records. Gated actions ensure you review and approve all proposed changes before any deletions or updates occur.

Yes, you can apply CI cleanup actions across an entire fleet or a single repository. The inventory identifies orphaned YAMLs, Dependabot auto-fixes, and stale runs, then gated actions implement the changes repeatably across the fleet.