BEAMdocs usebeam.sh →

Dependencies

Commands for expressing that one task waits on another. A blocked task shows its blocker in listings, and the daily views deprioritize it until the blocker clears.

block and unblock are top-level commands, not dep subcommands — both spellings of the same relationship.


dep

Aliases: deps
Purpose: Manage task dependencies.
Syntax:

dep add <blocker> <blocked>
dep rm <blocker> <blocked>
dep list <name-or-id>

Flags: none
Examples:

dep add #4 #7
dep list #7

See also: block, unblock, blocking

dep add #4 #7 reads "task #4 blocks task #7."


block

Aliases: none
Purpose: Mark a task as blocked by another.
Syntax:

block <task> <by-task>

Flags: none
Examples:

block #7 #4
block "send invites" "finalize guest list"

See also: unblock, dep

Sugar over dep add with the arguments in blocked-first order.


unblock

Aliases: none
Purpose: Remove a block between two tasks.
Syntax:

unblock <task> <by-task>

Flags: none
Examples:

unblock #7 #4

See also: block, dep


blocking

Aliases: none
Purpose: Show what a task is blocking.
Syntax:

blocking <name-or-id>

Flags: none
Examples:

blocking #4

See also: dep, block