Manual triggers run when you explicitly start them. Use them for one-time migrations, testing Automations before scheduling, or changes that need human judgment on timing. They are the safest way to develop a new Automation because you control exactly when it starts and can review the results before making it recurring or event-driven.Documentation Index
Fetch the complete documentation index at: https://ona.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
When to use manual triggers
Manual triggers are a good fit for:- trying a new Automation on a small set of targets
- maintenance work you want to supervise closely
- one-off repository sweeps
- workflows that should only run after a human decision
Configuration
Runs on
Projects (recommended)
Select one or more projects. The Automation runs on all repositories within them. Best for repetitive tasks on known repositories.Repositories
Use a search query to filter repositories. Best for large-scale migrations across many targets.| Query | Matches |
|---|---|
backend | Repositories with “backend” in name |
frontend- | Repositories starting with “frontend-” |
myorg/ | All repositories under “myorg” organization |
Choosing projects vs repository queries
- Projects are best when you already know the exact repositories and want them to use project-level configuration.
- Repository queries are best when you want to sweep a broader set of repositories without manually listing them.
Running
- Navigate to Automations
- Click your Automation
- Click Run
Review after the run
After a manual run, check:- which targets were selected
- whether the right repositories were included
- whether the actions produced the expected pull requests, comments, or reports