Epic delivery runs
Run an epic delivery pipeline when you want Helpin to coordinate code delivery for the open tasks in one epic. The run works through implementation, review, and integration, and finishes with a pull request that brings the epic's code together.
Start a delivery run
Open the epic and find its Delivery area.
Select Run delivery pipeline.
You need permission to edit the epic; the action can be unavailable for viewers or readers.
Before starting, review the epic's open tasks and their blocking links. The pipeline orders work using those links, so accurately marking blocked-by relationships helps the run work in a sensible order. Also check that each task has clear acceptance criteria and a suitable delivery configuration — repository and base branch — before you launch.
What the pipeline does
A delivery run works through the epic's open tasks in order:
It asks coding agents to implement task work.
It runs the review step for that work.
It merges the open task work onto the epic's integration branch.
The integration branch brings the task changes together before the final epic pull request is opened. This lets the run assemble the epic as one reviewable change instead of leaving you to merge many task pull requests by hand.
The pipeline focuses on open tasks, so finish or close work that should not be included first.
Follow progress and respond to problems
The Delivery panel lists runs for the epic. Select a run to open it for more detail.
Watch the current status and the task-level progress items.
If a run stalls, an editor can Resume it.
If it fails, an editor can Retry it after checking the affected task, delivery target, or dependencies.
Prepare the epic
Make sure each task has clear acceptance criteria and that the team has a suitable repository and branch configuration. You can also set or override delivery details on individual tasks where needed.
Related
Was this article helpful?