Skip to content

[schema-coverage] feat: Add schema coverage demo for max-turn-cache-misses field #40753

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
Jun 22, 2026
+31 −0
Merged

[schema-coverage] feat: Add schema coverage demo for max-turn-cache-misses field #40753

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
31 changes: 31 additions & 0 deletions schema-demos/schema-demo-max-turn-cache-misses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
description: Demonstrates the `max-turn-cache-misses` schema field
on:
workflow_dispatch:
permissions:
contents: read
engine: codex
max-turn-cache-misses: 5
timeout-minutes: 5
---

# Schema Demo: `max-turn-cache-misses`

This workflow was auto-generated to demonstrate usage of the
`max-turn-cache-misses` field in the gh-aw frontmatter schema. It exists solely
to achieve 100% schema feature coverage.

## What `max-turn-cache-misses` Does

Maximum number of consecutive AWF cache misses allowed before the API proxy
blocks further requests.

@github-actions github-actions Bot Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[/grill-with-docs] The What ... Does description omits the internal field mapping and default value that make similar demos more useful as reference documentation.

💡 Suggestion

Other demos include the internal mapping in their description. For example, schema-demo-max-runs.md reads:

Deprecated legacy alias for AWF invocation cap (apiProxy.maxRuns). Use max-turns instead.

The PR body template attempted to include this metadata (Maps to <field>. Precedence: frontmatter value → <env_var> env override → built-in default <default>.) but the placeholders were left empty, and that information did not make it into the committed file body either.

Consider enriching the description — something like:

Maximum number of consecutive AWF cache misses allowed before the API proxy
blocks further requests. Maps to `apiProxy.maxTurnCacheMisses`. Precedence:
frontmatter value → `AWF_MAX_TURN_CACHE_MISSES` env override → built-in default `10`.

(Adjust the field path, env var, and default to match the actual schema values.)

This makes the demo genuinely educational rather than just a coverage stub.


## Task

Call `noop` -- this is a coverage-only demo workflow.

**Important**: Always call the `noop` safe-output tool.

```json
{"noop": {"message": "Coverage demo for `max-turn-cache-misses` -- no action needed."}}
```
Loading