Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .donkeyspace/policy.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ workflow:
allow_labels:
- "ai"

engagement:
default:
allow:
- type: token_owner

agents:
triage:
enabled: true
Expand Down
5 changes: 3 additions & 2 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,9 @@ DONKEYSPACE_API_PROXY_TARGET=http://localhost:8080
# Use the same value in the GitHub webhook configuration.
DONKEYSPACE_WEBHOOK_SECRET=

# Required for private repository checkout, branch pushes, PR creation,
# creating missing donkeyspace labels, and applying pending GitHub labels/comments.
# Required by the secure default engagement policy and for private repository
# checkout, branch pushes, PR creation, labels, and comments. Invalid configured
# tokens make the API fail at startup.
DONKEYSPACE_GITHUB_TOKEN=

# Optional webhook-free GitHub ingestion. Comma-separate owner/repository names.
Expand Down
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,9 @@ If your credentials live elsewhere, pass them explicitly:
docker compose --env-file /path/to/secrets.env up -d --force-recreate worker
```

Without the token, GitHub writes remain pending and private-repo checkout fails.
Without the token, GitHub writes remain pending, private-repo checkout fails,
and the secure default engagement policy denies new AI work. The API validates
a configured token by resolving its authenticated user at startup.

When the token is configured, the worker ensures every configured workflow, allow, and block label exists in GitHub repositories already seen by donkeyspace webhooks.

Expand Down
Loading