GitHub Actions
Repository automation for validating content schemas, generated files, links, builds, and review gates.
- Published
- Updated
- Evidence checked
- Sources
- 2
At a glance
Use deterministic automation for deterministic checks. Keep editorial judgment and publication approval human.
- Record type
- Infrastructure
- Primary scope
- GitHub · continuous integration · content operations
- Evidence state
- Official documentation
- Record owner
- Marketing Wiki Editors
GitHub Actions runs workflows in response to repository events. Marketing content repository can use it to validate structure before human review.
Useful jobs#
- Validate metadata schema
- Reject duplicate slugs
- Regenerate machine-readable indexes
- Detect unexpected generated-file changes
- Build website
- Check internal links
- Report stale evidence dates
Boundary#
Workflow can prove file matches schema. It cannot prove recommendation is fair, evidence supports interpretation, or page deserves publication.
Keep agent permissions narrow. Content agent can propose branch. Workflow checks branch. Human reviewer approves merge.
Marketing Wiki use#
Current validation runs content generation, checks generated manifest, lints site, builds production output, and renders key routes. Main branch should require these checks after GitHub repository exists.
Evidence state#
Capability description comes from official GitHub documentation. No independent reliability or performance benchmark has been run for this index entry.