elastic / elastic/ai-github-actions
[aw] No-Op Runs
- Dominant language
- Python
- Stars
- 11
- Forks
- 16
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 31
Description
This issue tracks all no-op runs from agentic workflows in this repository. Each workflow run that completes with a no-op message (indicating no action was needed) posts a comment here.
What is a No-Op?
A no-op (no operation) occurs when an agentic workflow runs successfully but determines that no action is required. For example:
- A security scanner that finds no issues
- An update checker that finds nothing to update
- A monitoring workflow that finds everything is healthy
These are successful outcomes, not failures, and help provide transparency into workflow behavior.
How This Helps
This issue helps you:
- Track workflows that ran but determined no action was needed
- Distinguish between failures and intentional no-ops
- Monitor workflow health by seeing when workflows decide not to act
Resources
- [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw)
> [!TIP]
> To stop a workflow from posting here, set `report-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> noop:
> report-as-issue: false
> ```
---
> This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
>
> **No action to take** - Do not assign to an agent.
> - [x] expires on May 14, 2026, 5:25 PM UTC
Contributor guide
Assessment
This issue has not been assessed yet.