Recipes and sweeps
One change, across many repositories
A recipe is a named approach to a job teams repeat, such as a dependency upgrade or a config migration. Run it on one ticket, on a schedule, or across many repositories under one approval.
Ticket labelrecipe:dependency-upgrade
A recipe label on a ticket makes the run follow that recipe, with its parameters read from key: value lines in the ticket.
Five ship built in: dependency upgrade, API integration, test coverage, framework bump and config migration. Your organisation can write its own.
A schedule runs a recipe daily, weekly or monthly, in UTC, with its own per-run budget and a cap on runs per month.
A sweep runs one recipe across up to 50 repositories: one pull request per repository, one approval for all of them, and a budget, if you set one, split evenly between them.
Loosens a gate. A recipe can make review stricter, never lighter, and framework bumps and config migrations always wait for a person to approve the plan and the merge.
Starts a sweep before someone approves it. Until then it is a draft.
Catches up on missed runs. A schedule that was down for a week runs once when it returns.
A project for each repository, and the recipe's parameters in the ticket or the schedule.
Room in the project's automatic-run limits: scheduled runs count against them like any other.