git-annex-schedule(1)
π git-annex-schedule β get or set scheduled jobs π
okay bestie, this is a page from the General Commands Manual (yes, the git-annex-schedule(1) one, we're fancy now β¨). Sit down, grab a lil snack π, and let's talk about making your repos do chores on a schedule. it's giving "roomba but for fsck" and honestly? obsessed. π
β¨ NAME β¨
git-annex-schedule β get or set scheduled jobs ποΈ
π¦ SYNOPSIS π¦
git annex schedule repository [expression]
πΈ DESCRIPTION πΈ
So the git-annex-assistant(1) daemon can be configured to run scheduled jobs. π
Now, this is similar to cron and anacron β and lowkey if you prefer those, you can absolutely just use them instead, no hard feelings π«Ά β but the glow-up here is that it's integrated into git-annex. Which means it can do stuff like, oh you know, fsck a repository on a removable drive when the drive gets connected. the way that it just knows?? main character energy fr fr. π
When you run it with an expression, it configures scheduled jobs to run at a particular time. this is literally how you make the assistant periodically run incremental fscks. slay. π
When you run it without an expression, it just outputs the current scheduled jobs for that repository. no notes, just receipts. π
π§ EXPRESSIONS π§
These actions are available:
"fsck self""fsck UUID"β where UUID is the UUID of a remote to fsck π
After the action comes the duration to allow the action to run, and finally the schedule of when to run it. order matters, bestie, don't freestyle it. π
To schedule multiple jobs, separate them with "; " (that's a semicolon and a space, periodt). β¨
Some examples, copy-paste ready:
fsck self 30m every day at any time
fsck self 1h every month at 3 AM
fsck self 1h on day 1 of every month at any time
fsck self 1h every week divisible by 2 at any time
π OPTIONS π
The git-annex-common-options(1) can be used. that's it, that's the whole section. iconic minimalism. π€β¨
π SEE ALSO π
π AUTHOR π
Joey Hess <id@joeyh.name> β thank you king, we stan π
okay that's the whole page bestie, and this lil sign-off is standing in for the footer, which is just git-annex-schedule(1) from the General Commands Manual π (the manpage doesn't ship a version or date line, so that's all we've got, and we're not about to make one up β no cap). go forth and schedule responsibly, you got this ππ¦β¨
π¦ 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