Skip to content

[schema-coverage] feat: Add schema coverage demo for environment field#32980

Merged
pelikhan merged 1 commit into
mainfrom
schema-coverage-environment-96a8dabb911f4879
May 18, 2026
Merged

[schema-coverage] feat: Add schema coverage demo for environment field#32980
pelikhan merged 1 commit into
mainfrom
schema-coverage-environment-96a8dabb911f4879

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Schema Coverage Demo

This PR adds a minimal demo workflow that demonstrates usage of the environment field in the gh-aw frontmatter schema.

Why: The schema feature coverage checker found that environment was not used in any existing workflow.

What: Adds schema-demos/schema-demo-environment.md with a valid, minimal demonstration of this field.

Field Description

Environment that the job references (for protected environments and deployments).

Note

The demo uses production as a placeholder GitHub Actions environment name. A repository may need that environment configured before running this demo.

Validation

  • Coverage grep confirms schema-demos/schema-demo-environment.md now contains the top-level environment key.
  • make build && make fmt could not complete because this runner has Go 1.24.13 locally, while go.mod requires Go 1.25.8, and the toolchain download from proxy.golang.org is blocked by the environment firewall.
  • make fmt is blocked by the same missing Go 1.25.8 toolchain.

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 ·

  • expires on May 25, 2026, 7:55 AM UTC

@pelikhan pelikhan marked this pull request as ready for review May 18, 2026 12:48
Copilot AI review requested due to automatic review settings May 18, 2026 12:48
@pelikhan pelikhan merged commit b6e968a into main May 18, 2026
4 checks passed
@pelikhan pelikhan deleted the schema-coverage-environment-96a8dabb911f4879 branch May 18, 2026 12:48
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a minimal schema demo workflow to cover the top-level environment frontmatter field.

Changes:

  • Adds schema-demos/schema-demo-environment.md.
  • Demonstrates environment: production with the same minimal structure used by existing schema demos.
Show a summary per file
File Description
schema-demos/schema-demo-environment.md Adds a coverage-only demo for the environment schema field.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@github-actions github-actions Bot mentioned this pull request May 18, 2026
Copy link
Copy Markdown
Contributor Author

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Skills-Based Review 🧠

Applied /grill-with-docs — this PR introduces a new schema demo file, so I checked it against the project vocabulary and existing patterns.

Key Themes

  • Consistent with established pattern: The new schema-demo-environment.md is structurally identical to schema-demo-labels.md and schema-demo-metadata.md — same frontmatter shape, same noop-only task body, same auto-generated notice.
  • Correct field usage: environment: production is a valid string value for the environment key, which maps directly to the GitHub Actions environment concept described in the field description.

Positive Highlights

  • ✅ File name follows the schema-demo-<field>.md convention.
  • ✅ PR description clearly explains the why (coverage gap) and the caveat (repo must have a production environment configured).
  • ✅ Permissions are minimal (contents: read), appropriate for a no-op demo.

Verdict

Changes are clean and purposeful. Approving.

🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · ● 3.2M

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.

2 participants