git-locked

List all local locked files

$ git locked

git-locked [options] lock|unlock|status [file-or-ref]

-h, --help
    Display help and exit

-v, --verbose
    Enable verbose output

--force
    Force unlock (use with caution)

-r, --repo <path>
    Specify Git repository path

git-locked is not a built-in Git subcommand or standard Linux utility found in major distributions like Ubuntu, Fedora, or Arch Linux man pages. It appears to reference third-party tools or scripts designed to manage file or branch locks in shared Git repositories, preventing concurrent edits and merge conflicts.

Git itself uses internal lock files (e.g., .git/index.lock, .git/refs/heads/master.lock) during operations like commit or checkout to ensure atomicity. These locks are automatically removed on success but may persist if a process crashes. Users typically remove stale locks manually with caution using rm, risking data corruption if not careful.

Projects like git-lock (various GitHub repos) or integrations with Git LFS (git lfs lock) provide locking features for large files or workflows. If git-locked is from a specific package (e.g., installed via pip or npm), it likely offers commands to acquire/release locks on files or refs. Always verify the source for security. For standard Git, no such command exists; consider hooks or extensions for custom locking needs.

Usage example (hypothetical third-party): git-locked lock file.txt to lock a working tree file.

Not a standard command; third-party tools vary and may introduce security risks or incompatibilities. Manually handling Git locks can corrupt repositories. Prefer Git LFS locks for files or pre-commit hooks for workflows.

Git auto-manages locks during git add, git commit, etc. Stale locks: rm .git/index.lock only if no git process runs (ps aux | grep git).

Use git lfs lock FILE for large files; shell flock for scripts; or repo-specific hooks.

No official history as it's not core Git (developed by Linus Torvalds since 2005). Third-party locking tools emerged ~2010s for collaborative workflows, inspired by Git's internal .lock files. Git 2.x improved lock timeouts but no dedicated subcommand.

git(1), git-lfs(1), rm(1), flock(1)