🧹 GHCR Cleanup workflow (TangSengDaoDao/TangSengDaoDaoServer)
The 🧹 GHCR Cleanup workflow from TangSengDaoDao/TangSengDaoDaoServer, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the 🧹 GHCR Cleanup workflow from the TangSengDaoDao/TangSengDaoDaoServer repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: 🧹 GHCR Cleanup
on:
workflow_dispatch:
schedule:
- cron: '0 3 * * *'
permissions:
contents: read
packages: write
jobs:
cleanup:
runs-on: ubuntu-latest
steps:
- uses: rlespinasse/github-slug-action@v5
- name: 🔍 Cleanup GHCR
uses: dataaxiom/ghcr-cleanup-action@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
packages: ${{ env.GITHUB_REPOSITORY_NAME_PART_SLUG }}
delete-untagged: true
older-than: 30 days
delete-ghost-images: true
delete-partial-images: true
delete-orphaned-images: true
validate: true
log-level: info
dry-run: false
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: 🧹 GHCR Cleanup on: workflow_dispatch: schedule: - cron: '0 3 * * *' permissions: contents: read packages: write jobs: cleanup: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: rlespinasse/github-slug-action@v5 - name: 🔍 Cleanup GHCR uses: dataaxiom/ghcr-cleanup-action@v1 with: token: ${{ secrets.GITHUB_TOKEN }} packages: ${{ env.GITHUB_REPOSITORY_NAME_PART_SLUG }} delete-untagged: true older-than: 30 days delete-ghost-images: true delete-partial-images: true delete-orphaned-images: true validate: true log-level: info dry-run: false
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Add a job timeout so a hung step cannot burn hours of runner time.
2 third-party actions are referenced by a movable tag. Pin them to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.