Skip to content

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

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
schema-demo-max-turn-cache-misses-54b7470eb55de2d9
Draft

[schema-coverage] feat: Add schema coverage demo for max-turn-cache-misses field#40753
github-actions[bot] wants to merge 1 commit into
mainfrom
schema-demo-max-turn-cache-misses-54b7470eb55de2d9

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Schema Coverage Demo\n\nThis PR adds a minimal demo workflow that demonstrates usage of the field in the gh-aw frontmatter schema.\n\nWhy: The schema feature coverage checker found that was not used in any existing workflow.\n\nWhat: Adds with a valid, minimal demonstration of this field.\n\n### Field Description\n\nMaximum number of consecutive AWF cache misses allowed before the API proxy blocks further requests. Maps to . Precedence: frontmatter value → env override → built-in default .

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • proxy.golang.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "proxy.golang.org"

See Network Configuration for more information.

Generated by 📊 Schema Feature Coverage Checker · 3.51 AIC · ⌖ 7.99 AIC · ⊞ 25.5K ·

  • expires on Jun 29, 2026, 12:37 AM UTC-08:00

@github-actions

Copy link
Copy Markdown
Contributor Author

Hey @github-actions 👋 — thanks for the automated schema coverage demo for the max-turn-cache-misses field! The new file fits neatly into the established schema-demos/ pattern and the PR body clearly explains the field semantics and the coverage motivation.

One thing worth noting:

  • No test files in the diff — the Schema Feature Coverage Checker workflow generates the demo .md file, but there is no corresponding automated validation that the demo workflow itself can be parsed/linted without errors. If the coverage checker already validates the generated file before opening the PR, this is fine; if not, a quick schema-lint step would harden this flow.

If you would like to address that gap, here is a ready-to-use prompt:

Add a lightweight validation step to the Schema Feature Coverage Checker workflow that runs the gh-aw schema linter (or equivalent frontmatter parser) against every newly generated schema-demo-*.md file before opening a pull request. This ensures the generated files are syntactically valid and the max-turn-cache-misses (and future fields) are correctly formatted before the PR is created.

Generated by ✅ Contribution Check · 153 AIC · ⌖ 15.6 AIC · ⊞ 5.9K ·

@github-actions github-actions Bot mentioned this pull request Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants