AI coding workflow editor for your own pipeline

Open Workflows in the gear menu. There is a general workflow, and each project follows it unless it has its own.

Steps are the board columns: a plain Step, a Decision that takes the first arrow whose conditions hold, In parallel, which runs its actions together and moves on when all are done, or a Gate that holds the ticket until a person approves. To Do and the final step are fixed, and a workflow has at most 60 steps and 300 arrows.

Actions run when a ticket reaches a step: analyze, develop, create a pull request, check CI, review, merge to staging, run tests, merge (automatically or waiting for a person), comment, notify, request approval, security scan and wait (1 minute to 7 days). Actions that need a remote repository are skipped while the project has none.

Conditions sit on arrows and all of them must hold: a number of approvals, no changes requested, CI passed, has a pull request, ticket type (Feature, Bugfix, Hotfix), analysis viable or not, development done, deployed, tests passed, approved, scan passed or failed, waited.

Moving a ticket by hand needs an arrow whose conditions hold, and To Do is always reachable. When a step is removed, its tickets go back to To Do.

The Catalog lists Full pipeline (CI, code review, staging and testing before Done), Local (no remote repository, so no pull requests, CI or reviews), the workflows you save and the ones plugins publish. Using one gives the project its own copy, and Volath first shows how many tickets sit in steps the new workflow lacks.

The security scan action scans the lines a branch adds for secrets, risky dependencies and injections, and critical or high findings fail it.