Skip to content
All You Need Is Git

FAQ / Troubleshooting

aynig run does nothing

Common causes:

  • There is no dwp-state: trailer in HEAD.
  • The runner is scanning branches that have no actionable state.
  • Your command for the state does not exist.

Checks:

Terminal window
aynig status

Confirm:

  • dwp-state is present
  • command: exists

”command missing”

Your state foo must have an executable file:

.dwp/command/foo

Make it executable:

Terminal window
chmod +x .dwp/command/foo

“permission denied” running a command

  • Make sure the command is executable.
  • Ensure the script has a valid shebang:
#!/usr/bin/env bash

Worktrees keep accumulating

  • The default worktree directory is .worktrees/.
  • It is meant to be ephemeral and is ignored by default.

If you see leftovers after crashes, clean them:

Terminal window
rm -rf .worktrees/

Then run again.

”working” commits appear in history

This is the lease mechanism. The runner uses dwp-state: working to claim a branch.

See: Run and Operate → Leases and Liveness.

My workflow is stuck in working

A runner may have crashed. If the lease is expired, another runner can take over.

  • Inspect the latest commit trailers (dwp-run-id, dwp-lease-seconds).
  • Decide whether to continue or mark it stalled.

See: Guides → Ops Workflow Pack (stalled recovery).