git-annex-reinject(1)

💖 git-annex-reinject 💖

okay bestie, welcome to the git-annex-reinject(1) page from the General Commands Manual — yes it's a real one, yes it's a banger, let's get into it 🎀

---

✨ NAME ✨

git-annex-reinject — inject content of file back into annex 🦋

---

🌸 SYNOPSIS 🌸

git annex reinject [src dest]

git annex reinject --known [src]

---

💅 DESCRIPTION 💅

So basically: this command moves the content of the src file (or files!) into the annex. That's the whole vibe. But here's the catch — only known file contents will be reinjected. Any src files that are unknown? Left completely unchanged. Not touched. Not even a little. 🙈

When is this iconic? When you've obtained the content of a file from somewhere else and you want it in your local annex, fr fr. Like, say a file's content got lost 😭 and you have a backup — you restore that backup and reinject it into your local repository. Slay, data restored. 💖

There are two ways to use this, and you gotta pick one:

1. Specifying a src file and the name of a dest file (the dest lives inside the repository's working tree) — this injects the src file as the content of the dest file.

git annex reinject /tmp/foo.iso foo.iso

2. The --known option — this reinjects all known src files, and you don't even need to specify a dest file. Main character energy, no dest required. 👑

git annex reinject --known /tmp/*.iso

---

⭐ OPTIONS ⭐

• --known — with this option, each specified src file gets hashed using the default key-value backend (or the one you specify with --backend), and if git-annex has a record of the resulting key having been in the annex before, then the content gets reinjected. 🫶

heads up bestie, if you're using a key-value backend that includes the filename extension in the key, this will only work if the src files have the same extensions as the files with the same content that was originally added to git-annex. extension mismatch = no reinject, sorry 💀

also note: this will reinject old versions of files that have been modified or deleted from the current git branch. use git-annex-unused(1) to detect when such old and potentially unused files have been reinjected. lowkey important, don't skip this one. 👀

• --backend — specify the key-value backend to use when checking if a file is known with the --known option. 🌈
• --guesskeys — with this option, each specified source file is checked to see if it has the name of a git-annex key, and if so it is imported as the content of that key. it's giving detective energy 🔍

this can be used to pluck git-annex objects out of lost+found, as long as the original filename has not been lost, and it's particularly useful when using key-value backends that don't hash to the content of a file. ✨

when the key-value backend does support hashing, the content of the file is verified before importing it. safety first, always. 🎀

• --json — Enable JSON output. This is intended to be parsed by programs that use git-annex. Each line of output is a JSON object. 🤖
• --json-error-messages — Messages that would normally be output to standard error are included in the JSON instead. errors but make it JSON, periodt. 💅
• Also the git-annex-common-options(1) can be used. don't forget the classics bestie 💜

---

🦋 SEE ALSO 🦋

• git-annex(1)
• git-annex-add(1)
• git-annex-unused(1)
• git-annex-fsck(1)

---

👑 AUTHOR 👑

Joey Hess <id@joeyh.name>

---

okay that's the whole page, you ate that. this was the git-annex-reinject(1) page from the General Commands Manual, and yeah — the footer is literally just the same name again, git-annex-reinject(1), iconic of it honestly. go reinject something, bestie 🌸💖✨