Skip to content

[docs] Update glossary - daily scan #14754

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 1 commit into from
Feb 10, 2026
Merged

[docs] Update glossary - daily scan #14754

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions docs/src/content/docs/reference/glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -359,6 +359,30 @@ on:

Operational patterns (suffixed with "-Ops") are established workflow architectures for common automation scenarios. Each pattern addresses specific use cases with recommended triggers, tools, and safe outputs.

### ChatOps

Interactive automation triggered by slash commands (`/review`, `/deploy`) in issues and pull requests. Team members trigger workflows by typing commands directly in discussions, enabling human-in-the-loop automation where developers invoke AI assistance on demand.

**Use for:** Interactive code reviews, on-demand deployments, assisted analysis, and team collaboration through shared commands.

See [ChatOps](/gh-aw/patterns/chatops/) for implementation details.

### DailyOps

Scheduled workflows for incremental daily improvements that automate progress toward large goals through small, manageable changes. Work happens automatically on weekday schedules with changes easy to review and integrate.

**Use for:** Continuous code quality improvements, progressive migrations, documentation maintenance, and chipping away at technical debt one small PR at a time.

See [DailyOps](/gh-aw/patterns/dailyops/) for implementation details.

### DataOps

Hybrid pattern combining deterministic data extraction in `steps:` with agentic analysis in the workflow body. Shell commands reliably fetch and structure data, then the AI agent interprets results and produces insights.

**Use for:** Data aggregation from APIs or logs, report generation, trend analysis, and auditing workflows that gather evidence and generate reports.

See [DataOps](/gh-aw/patterns/dataops/) for implementation details.

### DispatchOps

Manual workflow execution via the GitHub Actions UI or CLI using the `workflow_dispatch` trigger. Enables on-demand tasks, testing, and workflows requiring human judgment about timing. Workflows can accept custom input parameters for runtime customization.
Expand Down Expand Up @@ -423,6 +447,14 @@ Maintaining and propagating W3C-style specifications using the `w3c-specificatio

See the [SpecOps](/gh-aw/patterns/specops/) for implementation details.

### TaskOps

Scaffolded AI-powered code improvement strategy with three phases: research agent investigates and reports findings, developer reviews and invokes planner agent to create actionable issues, then assigns approved issues to Copilot for automated implementation. Keeps developers in control with clear decision points at each phase.

**Use for:** Systematic code improvements requiring investigation before action, work needing breakdown for optimal AI agent execution, and situations where research findings vary in priority and require developer oversight.

See [TaskOps](/gh-aw/patterns/taskops/) for implementation details.

### TrialOps

Testing and validation pattern that executes workflows in isolated trial repositories before production deployment. Creates temporary private repositories where workflows run safely, capturing safe outputs without modifying your actual codebase.
Expand Down