git-annex-wanted(1)

🎀 git-annex-wanted(1) 🎀

okay bestie, pull up a chair, because this one is actually so fun. it's a page from the General Commands Manual and it's literally called git-annex-wanted — get or set preferred content expression. yes, you get to tell your repo what it wants. main character energy fr fr. 💅

✨ NAME ✨

git-annex-wanted — get or set preferred content expression

🌸 SYNOPSIS 🌸

git annex wanted repository [expression]

🦋 DESCRIPTION 🦋

So here's the tea. ☕

When you run it with an expression, it configures the content that is preferred to be held in the repository. like, "hey repo, this is the vibe you should be chasing." and for the full deets on how to write those expressions, go read git-annex-preferred-content(1). iykyk. 📖

For example:

git annex wanted here "include=*.mp3 or include=*.ogg"

look at that. absolutely ate. now here wants your music files. 🎧

Without an expression, it just displays the current preferred content setting of the repository. no changes, no drama, just receipts. 👀

And if you wanna return a repository to the original default behavior, you use an empty value for the expression, eg:

git-annex wanted here ""

poof, back to factory settings. the way that empty string just resets everything?? iconic. ✨

💖 OPTIONS 💖

• The git-annex-common-options(1) can be used.

that's the whole list bestie. common options only. sometimes less is more, periodt. 💅

👑 SEE ALSO 👑

• git-annex(1)
• git-annex-required(1)
• git-annex-preferred-content(1)
• git-annex-groupwanted(1)

🌈 AUTHOR 🌈

Joey Hess <id@joeyh.name>

and that's the whole page, bestie!! 🫶 written by the legend himself, Joey Hess <id@joeyh.name>, and this lil beauty lives in the General Commands Manual as git-annex-wanted(1). go set some preferences and slay the day away. 💜🎀✨