git-annex-...kpresentkey(1)

πŸ“¦
version 10.20261026 Β· 2 versions
  • 10.20261026 Β· alpine 3.24, arch rolling, debian bookworm, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 8.20210223 Β· ubuntu jammy
, in alpine 3.24, arch rolling, debian bookworm, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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 0 if the content is verified present in the remote β€” slay, it's there πŸŽ‰
  • exits 1 if it is verified to not be present in the remote β€” rip, it's gone 😭
  • if there's a problem, the special exit code 100 is used, and an error message is output to stderr. so 100 means something went wrong, not just "nope, not here."
fr fr, don't mix up 1 and 100. 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 from stdin, 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. πŸ’…βœ¨πŸ«Ά