git-annex-...kpresentkey(1)
π git-annex-checkpresentkey π
okay bestie, so this is one of the pages from the git-annex manual β that big gorgeous General Commands Manual situation β and it's all about git-annex-checkpresentkey, aka the lil detective that checks if a key is present in a remote. it's giving plumbing-level realness and honestly? obsessed. π΅οΈββοΈβ¨
πΈ NAME πΈ
git-annex-checkpresentkey β check if key is present in remote
β¨ SYNOPSIS β¨
git annex checkpresentkey key [remote]
π¦ DESCRIPTION π¦
so this is a plumbing-level command (iykyk, it's the low-level stuff the fancy commands build on), and what it does is verify if the specified key's content is present in the specified remote. like, is the thing actually there or not. vibe check on your data, basically. π
when you don't specify a remote, it verifies if the key's content is present in any accessible remotes. so it'll go looking around everywhere, no cap. π
the exit codes are the whole story here, so listen up:
- exits
0if the content is verified present in the remote β slay, it's there π - exits
1if it is verified to not be present in the remote β rip, it's gone π - if there's a problem, the special exit code
100is used, and an error message is output tostderr. so100means something went wrong, not just "nope, not here."
fr fr, don't mix up1and100. one of them is a normal answer and the other one is the command going "girl help something is broken". π
π OPTIONS π
--batchβ enables batch mode. in this mode, the key is not specified at the command line, but the remote may still be. lines containing keys are read fromstdin, and a line is output with"1"if the key is verified to be present, and"0"otherwise. it's the "give me a whole list and I'll answer each one" era, and honestly it ate. π
also the git-annex-common-options(1) can be used. those are the shared ones, so go peek at that page if you want the full menu. π
π SEE ALSO π
π AUTHOR π
Joey Hess <id@joeyh.name> β the icon who wrote this, we stan. π
okay that's the whole page!! this was git-annex-...kpresentkey(1) from the General Commands Manual (yes the title really is spelled like that, we love a chaotic filename), and if you're seeing the version/date info down at the bottom, that's just the footer doing its little thing β go forth and check those keys, bestie. π
β¨π«Ά
π¦ where this page comes from
- alpine 3.24: git-annex-doc 10.20261026-r0 Β· AGPL-3.0-or-later
- arch rolling: git-annex 10.20261026-2 Β· AGPL-3.0-only
- debian bookworm: git-annex 10.20230126-3 Β· AGPL-3.0-or-later
- debian trixie: git-annex 10.20250416-2 Β· AGPL-3.0-or-later
- debian trixie: git-annex 10.20250416-2+deb13u1 Β· AGPL-3.0-or-later
- epel 10: git-annex 10.20250320-1.el10_0 Β· AGPL-3.0-or-later
- fedora 43: git-annex 10.20250630-4.fc43 Β· AGPL-3.0-or-later
- fedora 43: git-annex 10.20250929-5.fc43 Β· AGPL-3.0-or-later
- fedora 44: git-annex 10.20260115-1.fc44 Β· AGPL-3.0-or-later
- nixos 26.05: git-annex 10.20260421
- nixpkgs unstable: git-annex 10.20260421
- opensuse-leap 16.0: git-annex 10.20250828-bp160.1.1 Β· AGPL-3.0-or-later AND GPL-3.0-or-later AND BSD-2-Clause AND MIT AND GPL-2.0-only
- opensuse-leap 16.0: git-annex 10.20250828-bp160.1.1 Β· AGPL-3.0-or-later AND GPL-3.0-or-later AND BSD-2-Clause AND MIT AND GPL-2.0-only
- opensuse-leap 16.0: git-annex 10.20250828-bp160.1.1 Β· AGPL-3.0-or-later AND GPL-3.0-or-later AND BSD-2-Clause AND MIT AND GPL-2.0-only
- ubuntu noble: git-annex 10.20240129-1build1 Β· AGPL-3.0-or-later
- ubuntu questing: git-annex 10.20250721-1
- ubuntu resolute: git-annex 10.20251029-1ubuntu1 Β· AGPL-3.0-or-later
- ubuntu stonking: git-annex 10.20251029-1ubuntu1 Β· AGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms