Latest stable
Slack and GitHub integrations
Bring Slack messages or GitHub issues into kanban and return completed responses to their source thread.
When to use it
A team has reviewed token scopes, labels/channels, and the response/closure policy.
When not to use it
Do not enable bidirectional writes with unreviewed credentials or task-closing behavior.
Prerequisites
Slack bot or GitHub token environment variables and access to the selected channel/repository.
Representative command
Safety contract
Start with dry-run, least-privilege credentials, and narrow labels/channels. Keep secrets out of content and task bodies.
Artifacts to inspect
Tagged kanban tasks, integration state, source identifiers, and posted threaded responses/comments.
Troubleshooting
Verify scopes, repository/channel identifiers, tags, and state before continuous mode.
Freshness source
Reviewed against YYLO README: slack-integration and the generated installed-script inventory.