Repository navigation
[aw-daily] GAP-003: Add on.stale-check: sub-field to frontmatter-schema.md (v0.68.3) #27
Description
Gap Details
Type: missing
File: skills/aw-author/references/frontmatter-schema.md
Section: Section 2 Triggers — on: sub-fields
Current Content
The on: section documents trigger types (issues, pull_request, schedule, etc.) but does not document the stale-check: sub-field.
Expected Content
Add to the on: sub-fields section:
**`stale-check:`** — Boolean, default `true`. Controls whether the activation job verifies that the frontmatter hash matches the compiled workflow.
When `false`, disables the hash check step. Required when workflow files are managed outside the default repository context (e.g., cross-repo org rulesets where the compiled `.lock.yml` and the source `.md` are in different repos).
```yaml
on:
schedule:
- cron: '0 9 * * *'
stale-check: false
## Source
PR #26607 in github/gh-aw: [Sync github-agentic-workflows.md with v0.68.3](https://github.com/github/gh-aw/pull/26607)
## Intelligence Report
https://github.com/zircote/github-agentic-workflows/discussions/24
---
_Automated by /aw-daily on 2026-04-16_
Activity
docs(references): daily intelligence update 2026-04-16
docs(references): daily intelligence update 2026-04-16 (#30)
zircote commentedon Apr 16, 2026
Fixed in #30 (merged to
developon 2026-04-16). Theon.stale-check:sub-field is now documented inskills/aw-author/references/frontmatter-schema.md.Closing manually because GitHub's auto-close keywords only fire on merges to the default branch (
main). The change will reachmainon the next/aw-merge(develop → main).