CI Secret Cleanup: Remove Repository Variables Nobody Uses

CI secret cleanup starts in repository settings, workflow files, deployment environments, and release jobs. A variable that looks unused can still sign packages, publish images, open tunnels, or unlock production deploys.

The useful output is a CI secret retirement record with workflow references, access evidence, scope change, rotation result, and revoke date. Keep the review concrete: Rotate before deleting secrets used by release or deploy jobs, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when deleting a credential still used by release automation.

Key takeaways

Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
Use one release cycle plus the longest scheduled workflow and branch-support window before deciding that “quiet” means “unused.”
Prefer reversible changes first when deleting a credential still used by release automation is still plausible.
Leave behind a CI secret retirement record with workflow references, access evidence, scope change, rotation result, and revoke date so the next review starts with context.
Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.

Map Workflow Consumers

Start with one repository or CI organization across workflow files, environment variables, secret scopes, release jobs, deployment targets, and audit logs. 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	last use, permission scope, owner, rotation age, and reachable systems
Dependency evidence	audit logs, deployment references, identity provider records, and service owners
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.

Secret Evidence to Collect

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 secret cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Workflow references	YAML expressions, reusable workflows, actions, scripts, and environment mappings	No workflow reads the variable name
Last use	Secret access logs, job history, deploy records, and failed authentication attempts	The value has no legitimate recent use
Scope and privilege	Repository, organization, environment, branch, and protected-deploy access	The secret is broader than any current job needs
Rotation state	Replacement secret, dual-read window, rollback plan, and downstream token metadata	Jobs can move before the old value is revoked

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 Evidence Check

Search workflow references and scripts before deleting a repository or organization secret.

rg "secrets\.|vars\.|env:" .github .gitlab ci
rg "SIGNING_KEY|PUBLISH_TOKEN|DEPLOY_TOKEN|REGISTRY_PASSWORD" .github scripts docs
rg "workflow_call|reusable|environment:" .github/workflows

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.

Rotate Before Removing

Use the least permanent move that proves the decision. In CI secret cleanup, 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.

Rotate before deleting secrets used by release or deploy jobs.
Reduce scope from organization to repository or environment when use is unclear.
Remove old variable names from docs, examples, reusable workflows, and runner images.

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.

Release Credentials That Hide

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

Package publishing, code signing, production deploys, and vendor integrations.
Reusable workflows called by repositories outside the obvious project.
Self-hosted runners or old branches with cached environment assumptions.

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 CI Secret Review

Run CI secret cleanup 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 CI secret retirement record with workflow references, access evidence, scope change, rotation result, and revoke 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.

Scope Secrets at Creation

Prevention should change the creation path, not just the cleanup path. For CI secret cleanup, the useful prevention fields are owner, expiry date, least-privilege scope, rotation schedule, and removal notes. Make those fields part of normal creation and review.

Create CI secrets with owner, scope, consumer workflow, rotation path, and expiry.
Fail review for new secrets that are not referenced by code or deployment docs.
Audit organization-level secrets during repository archival and platform migrations.

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 CI secrets and variables in source control and CI systems
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Workflow references, Last use, and owner confirmation
First reversible move	Rotate before deleting secrets used by release or deploy jobs
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 release cycle plus the longest scheduled workflow and branch-support window
Prevention rule	Create CI secrets with owner, scope, consumer workflow, rotation path, and expiry

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 secret cleanup?

Use one release cycle plus the longest scheduled workflow and branch-support window 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, rotate before deleting secrets used by release or deploy jobs. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to package publishing, code signing, production deploys, and vendor integrations. 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.