docs: Add comprehensive documentation for agentic workflows and repos…

[mechonwheelssocal-jpg]

…itory audits

Summary

Add foundational documentation and analysis for agentic workflows, Pages templates coverage, and GHES sync policy to clarify the new AI-powered workflow category and identify gaps in static site generator support.

Changes

New Files

1. AGENTIC_WORKFLOWS.md - Comprehensive guide for agentic workflows

   • Explains markdown format and why it differs from traditional YAML workflows
   • Documents all 11 agentic workflows with use cases
   • Covers safety constraints, customization, stability status
   • Provides troubleshooting and recipes

2. PAGES_AUDIT.md - Analysis of static site generator coverage

   • Current: 9 templates (Jekyll, Hugo, Next.js, Nuxt, Astro, Gatsby, mdBook, static)
   • Gap analysis identifies 8 missing frameworks by priority
   • Critical recommendations: VitePress, Docusaurus, MkDocs
   • Demand signals and implementation effort for each candidate

3. GHES_SYNC_POLICY.md - Clarifies GHES synchronization constraints

   • Documents why 40 workflows (agentic + deployments) are excluded
   • Technical reasons: missing managed agent support, format incompatibility
   • Timeline: No public roadmap for GHES agentic support yet
   • Current sync covers 144/188 workflows (76%)

Modified Files

1. README.md - Updated workflow format section
   • Clarified that traditional workflows use YAML/YML
   • Noted that agentic workflows use Markdown with YAML frontmatter
   • Added reference to AGENTIC_WORKFLOWS.md for detailed guidance

Why This Matters

• Immediate clarity: Agentic workflows are new (May 2026) and need clear documentation
• Governance: Establishes why certain workflows are excluded from GHES
• Planning: Provides roadmap for expanding Pages category with high-demand tools
• Contributor guidance: Clarifies file format expectations and constraints

Next Steps (from review plan)

• Short-term: Evaluate agentic workflow adoption metrics
• Short-term: Plan Pages expansion (VitePress, Docusaurus, MkDocs candidates)
• Long-term: Monitor GHES support timeline and update policy accordingly

Pre-requisites

• Prior to submitting a new workflow, please apply to join the GitHub Technology Partner Program: partner.github.com/apply.

---

Please note that at this time we are only accepting new starter workflows for Code Scanning. Updates to existing starter workflows are fine.

---

Tasks

For all workflows, the workflow:

• Should be contained in a .yml file with the language or platform as its filename, in lower, kebab-cased format (for example, docker-image.yml). Special characters should be removed or replaced with words as appropriate (for example, "dotnet" instead of ".NET").
• Should use sentence case for the names of workflows and steps (for example, "Run tests").
• Should be named only by the name of the language or platform (for example, "Go", not "Go CI" or "Go Build").
• Should include comments in the workflow for any parts that are not obvious or could use clarification.
• Should specify least privileged permissions for GITHUB_TOKEN so that the workflow runs successfully.

For CI workflows, the workflow:

• Should be preserved under the ci directory.
• Should include a matching ci/properties/*.properties.json file (for example, ci/properties/docker-publish.properties.json).
• Should run on push to branches: [ $default-branch ] and pull_request to branches: [ $default-branch ].
• Packaging workflows should run on release with types: [ created ].
• Publishing workflows should have a filename that is the name of the language or platform, in lower case, followed by "-publish" (for example, docker-publish.yml).

For Code Scanning workflows, the workflow:

• Should be preserved under the code-scanning directory.
• Should include a matching code-scanning/properties/*.properties.json file (for example, code-scanning/properties/codeql.properties.json), with properties set as follows:
  • name: Name of the Code Scanning integration.
  • creator: Name of the organization/user producing the Code Scanning integration.
  • description: Short description of the Code Scanning integration.
  • categories: Array of languages supported by the Code Scanning integration.
  • iconName: Name of the SVG logo representing the Code Scanning integration. This SVG logo must be present in the icons directory.
• Should run on push to branches: [ $default-branch, $protected-branches ] and pull_request to branches: [ $default-branch ]. We also recommend a schedule trigger of cron: $cron-weekly (for example, codeql.yml).

Some general notes:

• This workflow must only use actions that are produced by GitHub, in the actions organization, or
• This workflow must only use actions that are produced by the language or ecosystem that the workflow supports. These actions must be published to the GitHub Marketplace. We require that these actions be referenced using the full 40 character hash of the action's commit instead of a tag. Additionally, workflows must include the following comment at the top of the workflow file:

  # This workflow uses actions that are not certified by GitHub.
  # They are provided by a third-party and are governed by
  # separate terms of service, privacy policy, and support
  # documentation.
  

• Automation and CI workflows should not send data to any 3rd party service except for the purposes of installing dependencies.
• Automation and CI workflows cannot be dependent on a paid service or product.