> ## Documentation Index
> Fetch the complete documentation index at: https://developer.upsun.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Built-in workflows

> Use Upsun Dispatch built-in workflows to turn issues into pull or merge requests, review pull or merge requests, and scan repositories for CVEs.

Upsun Dispatch includes built-in workflows for common development tasks. Use this page as a quick catalog of what each workflow does and what starts it.

> [!NOTE]
>
> Before you use a workflow, connect the relevant integrations and add an organization AI model key. See [Set up GitHub](https://developer.upsun.com/dispatch/docs/integrations/github.md), [Set up GitLab](https://developer.upsun.com/dispatch/docs/integrations/gitlab.md), [Set up Jira](https://developer.upsun.com/dispatch/docs/integrations/jira.md), [Set up Linear](https://developer.upsun.com/dispatch/docs/integrations/linear.md), and [AI models](https://developer.upsun.com/dispatch/docs/models).

## Workflow catalog

| Workflow | Supported sources | What starts it | What Upsun Dispatch publishes |
| - | - | - | - |
| [Issue to code](https://developer.upsun.com/dispatch/docs/workflows/issue-to-code.md) | GitHub issues, Jira issues, and Linear issues | The entire issue body or a single comment is exactly `@upsun-dispatch implement`, with an optional trailing `!`, `.`, or `?`. Issue to code has no automatic mode of its own. | A plan, generated implementation, critic review, pull or merge request when supported by your version control integration, and link-back comment. See [Integrations](https://developer.upsun.com/dispatch/docs/integrations.md) for supported publish targets. |
| [Code review](https://developer.upsun.com/dispatch/docs/workflows/code-review.md) | GitHub pull requests and GitLab merge requests | Supported pull request or merge request activity when automatic Code review is enabled, or a supported manual review command in a pull request or merge request comment | Review feedback such as check runs, review comments, merge request notes, commit statuses, and summaries |
| [CVE scan](https://developer.upsun.com/dispatch/docs/workflows/cve-scan.md) | GitHub repositories and GitLab projects | Manual scan from a repository workflow page, or a scheduled daily scan for that repository | One tracker issue per repository, kept up to date with the vulnerable dependencies, and the repository's latest **Security** results. See [CVE scan](https://developer.upsun.com/dispatch/docs/workflows/cve-scan.md) for scan behavior and result details. |

## Ticketing integrations

Issue to code can use ticketing integrations as issue sources. Connect Jira with [Set up Jira](https://developer.upsun.com/dispatch/docs/integrations/jira.md) or Linear with [Set up Linear](https://developer.upsun.com/dispatch/docs/integrations/linear.md) before starting issue-based work from those tools.

For Jira-triggered Issue to code, include the target repository as `owner/repo` or a full repository URL in the Jira issue description. See [Start from an issue or ticket](https://developer.upsun.com/dispatch/docs/workflows/issue-to-code.md#start-from-an-issue-or-ticket) for details.

## View and manage workflow runs

Use the [Upsun Dispatch console](https://developer.upsun.com/dispatch/docs/dashboard.md) to view repositories, follow runs and logs, inspect results, re-run eligible finished runs, and adjust workflow settings or repository overrides.

For the workflow settings that control built-in workflows, see [Workflows in Upsun Dispatch](https://developer.upsun.com/dispatch/docs/workflows.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.