CI Reusable Workflow Cleanup: Remove Legacy Docker Publish Jobs After Registry Migration

CI reusable workflow cleanup starts when shared jobs remain callable after pipelines, languages, or release policies change. A reusable workflow is easy to forget because it lives in one repository while risk appears in every downstream repo that still calls it.

For stale reusable CI workflows for Docker image publishing, the review should connect current use, ownership, dependencies, and reversibility before removal. The useful output is a reusable workflow cleanup record with caller inventory, secret/input map, migration status, replacement job, and deletion date: Deprecate shared workflows before deleting callable files, then make the final decision easy to audit later.

Key takeaways

Review stale reusable CI workflows for Docker image publishing through Caller inventory, Secret and input use, Support window, not age alone.
Use one CI cycle across default, release, scheduled, and manually triggered workflows before deciding that quiet means unused.
Start with the reversible move: deprecate shared workflows before deleting callable files.
Slow down when breaking downstream publishing or preserving shared registry credentials nobody maintains is still plausible.
Prevent repeat cleanup by making teams create reusable workflows with owner, support window, caller contract, and deprecation process.

Map Workflow Callers

Start with one reusable workflow across workflow_call references, downstream repositories, release branches, secrets, matrices, and build artifacts. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	owners, callers, last change, runtime behavior, and deletion confidence
Dependency evidence	repository search, tests, logs, deploy history, and owner review
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Reusable Workflow Evidence

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For CI reusable workflow cleanup for Docker publish jobs, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Caller inventory	workflow_call references, repository search, branch filters, and scheduled jobs	No supported pipeline calls the workflow
Secret and input use	Required secrets, inputs, outputs, environment names, and permission blocks	The workflow no longer protects or publishes current artifacts
Support window	Release branches, product support policy, runtime targets, and downstream maintainers	Old callers can safely move or close
Replacement job	New workflow, migration guide, required checks, and test run	Downstream repositories have a current path

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Example Reusable Workflow Review

Search workflow_call references and required secrets before deleting shared CI jobs.

rg "uses: .*/.github/workflows/|workflow_call|secrets:" .github repos docs
rg "$WORKFLOW_FILE|$WORKFLOW_NAME" .github repos docs
rg "release branch|schedule:|workflow_dispatch|required check" .github docs

Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.

Deprecate Before Deleting

Use the least permanent move that proves the decision. In CI reusable workflow cleanup for Docker publish jobs, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

Deprecate shared workflows before deleting callable files.
Migrate high-risk callers and release branches before low-risk repos.
Remove secrets and permission grants after the final caller moves.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Repos Still Calling Shared Jobs

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Release signing, package publishing, deployment, and compliance evidence workflows.
Repositories outside the obvious organization or branch.
Reusable workflows that expose outputs consumed by later jobs.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the Shared CI Cleanup

Run CI reusable workflow cleanup for Docker publish jobs as a decision review, not an open-ended hygiene project.

Pick the narrow scope and export the candidate list.
Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
Apply the least permanent useful change first.
Watch the signals that would reveal a bad decision.
Complete the final removal only after the review window closes.
Save a reusable workflow cleanup record with caller inventory, secret/input map, migration status, replacement job, and deletion date.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Give Shared Jobs Support Windows

Prevention should change the creation path, not just the cleanup path. For CI reusable workflow cleanup for Docker publish jobs, the useful prevention fields are owner, reason to exist, removal trigger, and verification notes. Make those fields part of normal creation and review.

Create reusable workflows with owner, support window, caller contract, and deprecation process.
Generate caller inventories from repository search or CI metadata.
Review shared jobs when release policies, runtimes, or runner fleets change.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Stale reusable CI workflows for Docker image publishing in source repositories, workflow callers, container registries, release branches, secrets, and shared build automation
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Caller inventory, Secret and input use, and owner confirmation
First reversible move	Deprecate shared workflows before deleting callable files
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after one CI cycle across default, release, scheduled, and manually triggered workflows
Prevention rule	Create reusable workflows with owner, support window, caller contract, and deprecation process

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do CI reusable workflow cleanup for Docker publish jobs?

Use one CI cycle across default, release, scheduled, and manually triggered workflows for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, deprecate shared workflows before deleting callable files. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to release signing, package publishing, deployment, and compliance evidence workflows. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.