Find which Linux directory consumes inodes before cleanup
Inode exhaustion usually comes from many directory entries rather than large bytes, so file counts and ownership matter more than du size.
Find large files on Linux without crossing the wrong filesystem
Du summarizes reachable directory entries while find can select individual files; mount boundaries and permissions determine what either command can see.
Use git bisect with a deterministic regression test
Bisect performs binary search between known good and bad commits, classifying tested revisions until it identifies the first bad candidate.
Create a Git bundle that proves it contains the refs needed for recovery
Git bundle writes selected reachable objects and refs into one file that another Git repository can verify and clone without network access.
Use Git interactive rebase without rewriting unreviewed shared history
Interactive rebase replays selected commits onto a new base, creating new object IDs and requiring explicit conflict and publication decisions.
Recover a lost Git commit from the reflog without moving the current branch
Reflogs record recent local ref movements and HEAD transitions, allowing a still-present commit object to be named and protected with a new ref.
Use git rerere to reuse conflict resolutions without trusting them blindly
Rerere records the shape of a conflict and the chosen resolution, then can reapply it when the same conflict recurs.
Restore a deleted Git branch from a verified commit object
Deleting a branch removes a ref, not immediately its reachable commit objects; reflogs, remotes, and object traversal may still identify the tip.
Use Git sparse-checkout for large repositories without losing tracked state
Sparse-checkout controls which tracked paths populate the working tree; cone mode uses directory patterns while the complete index and object model remain repository-wide.
Update Git submodules to reviewed commits instead of floating branches
A superproject records one gitlink commit for each submodule; update materializes that exact object according to local URL and recursion policy.
Verify signed Git commits while checking the trusted identity separately
A commit signature proves control of a signing key over one commit object; trust, key ownership, repository authorization, and source review remain separate.
Use git worktree for a clean hotfix without stashing active work
A linked worktree checks out another branch into a separate directory while sharing repository objects and most refs.
Attest GitHub Actions build artifacts and verify before deployment
An artifact attestation binds subject identity and digest to signed provenance generated by a workflow; deployment must still verify the expected repository and policy.
Prevent overlapping GitHub Actions deployments with one environment key
A concurrency group allows one running and one pending job or workflow per key; cancel-in-progress determines whether a newer run interrupts active work.
Design a GitHub Actions rollback job that does not rebuild history
A rollback should select a previously verified immutable artifact, pass the same environment gate, deploy through the same mechanism, and record a new deployment event.
Use GitHub Actions environment approval as a real deployment boundary
An environment can gate jobs with reviewers, branch rules, and protection rules; environment secrets are withheld until configured protection passes.
Manage SSH known_hosts in GitHub Actions without trusting the scan itself
Ssh-keyscan retrieves offered host keys without authenticating them, so CI must compare a pinned fingerprint delivered through an independent trust path.
Replace long-lived GitHub Actions cloud keys with constrained OIDC
A job with id-token write can request a short-lived signed token whose claims the cloud provider maps to a narrowly scoped role.
Build a reusable GitHub Actions deployment workflow with a narrow contract
Workflow_call defines typed inputs, secrets, permissions, and outputs so repositories can reuse reviewed deployment logic without copying mutable shell blocks.
Mask GitHub Actions secrets without treating redaction as containment
GitHub masks registered secret values in logs, but transformed, encoded, structured, or dynamically fetched values may need explicit masking and should not be printed at all.
Harden GitHub Actions self-hosted runners as disposable execution hosts
Self-hosted jobs execute on infrastructure you control and may persist processes, files, credentials, and network reachability unless each job receives an isolated ephemeral environment.
Build a GitHub Actions SSH deployment with a narrow remote command
An SSH deployment job should deliver an immutable artifact and invoke a reviewed least-privilege remote entrypoint rather than streaming arbitrary repository shell into production.
Validate the complete HAProxy configuration before reload
Haproxy -c parses the supplied configuration and referenced files using the installed binary without starting listeners.
Verify an HAProxy graceful reload across old and new workers
A graceful reload starts a validated new process and asks the old process to stop accepting new connections while it finishes existing work.