Workflows

Workflows let you queue a sequence of GitHub issues and have the bot work through them one at a time, automatically advancing to the next issue once the current one is closed.

What it does

Without workflows, you assign the bot to individual issues independently. With workflows, you define an ordered list of issues upfront. The bot finishes one, then moves straight to the next without any manual re-assignment between steps.

Creating a workflow

Open the dashboard and navigate to a repository’s task runs page.
Click Workflows in the sidebar.
Click the + button to open the issue picker dialog.
The dialog has two panels: open issues on the left, your queue on the right. Click an issue to add it. Drag to reorder. Click × to remove one.
Click Create Workflow.

The bot then:

Validates that every issue exists and is open.
Assigns itself to the first issue.
Posts a comment on every queued issue explaining its position in the queue.

How the bot advances through the queue

When an issue is closed, the bot automatically moves to the next one:

It checks whether a workflow is waiting on the just-closed issue.
If found, it advances to the next issue in the queue.
If the next issue is already closed (resolved out-of-band), the bot skips it and keeps advancing until it finds an open issue or reaches the end.
Once an open next issue is found, the bot assigns itself to it.
When the last issue is closed, the workflow is marked complete.

Guard: all preceding issues must be closed

Before starting work on any issue in a workflow, the bot checks that all preceding issues in the queue are already closed. If any are still open, it posts a comment listing the blockers and waits.

This prevents the bot from jumping ahead even if issues are manually assigned out of order.

Limitations

Only one active workflow per repository at a time. Attempting to create a second returns an error.
All issues must be open at creation time. Closed issues are rejected.
Issue numbers must be unique within a workflow.