Skip to content

docs: sharpen workflow-authoring guidance for PR scoping, backend compatibility checks, and coverage fallback networking#39622

Merged
pelikhan merged 3 commits into
mainfrom
copilot/agent-persona-exploration-again
Jun 16, 2026
Merged

docs: sharpen workflow-authoring guidance for PR scoping, backend compatibility checks, and coverage fallback networking#39622
pelikhan merged 3 commits into
mainfrom
copilot/agent-persona-exploration-again

Conversation

Copilot AI commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Persona exploration found the routing guidance was strong overall, with targeted gaps in PR path-scoping examples, backend schema/API review instructions, and fallback coverage network policy. This PR tightens those guidance points in the authoring docs used to generate workflows.

  • Create workflow guidance (.github/aw/create-agentic-workflow.md)

    • Expanded the PR scenario from schema-only to schema/API contract review.
    • Added explicit pull_request.paths scoping examples for backend contract surfaces (db/migrate/**, migrations/**, schema/**, openapi/**, api/**).
    • Added compact backend-review guidance: classify changes as additive / backward-compatible / breaking, and emit actionable risks only.
    • Strengthened the scoping checklist to explicitly require backend contract globs for backend-review automations.
  • Coverage workflow guidance (.github/aw/test-coverage.md)

    • Clarified fallback behavior when artifacts are missing: infer ecosystem from repo files and require network.allowed = [defaults + ecosystem].
    • Explicitly disallowed fallback coverage runs with network: defaults alone.
    • Added a compact YAML example for fallback network config.
network:
  allowed:
    - defaults
    - node

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Investigate agent persona scenarios and findings docs: sharpen workflow-authoring guidance for PR scoping, backend compatibility checks, and coverage fallback networking Jun 16, 2026
Copilot AI requested a review from pelikhan June 16, 2026 17:53
@pelikhan pelikhan marked this pull request as ready for review June 16, 2026 18:06
Copilot AI review requested due to automatic review settings June 16, 2026 18:06
@pelikhan pelikhan merged commit 4d91040 into main Jun 16, 2026
@pelikhan pelikhan deleted the copilot/agent-persona-exploration-again branch June 16, 2026 18:06

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates internal workflow-authoring guidance used by gh-aw to generate/shape agentic workflows, focusing on (1) tighter PR trigger scoping for backend contract reviews and (2) safer network policy expectations for fallback coverage runs.

Changes:

  • Expanded the “schema review” scenario into a schema/API contract review pattern, with concrete pull_request.paths scoping examples for backend contract surfaces.
  • Added compact backend-review guidance to classify contract changes (additive / backward-compatible / breaking) and report only actionable risks.
  • Clarified fallback coverage guidance to require inferring repo ecosystem and expanding network.allowed beyond defaults.
Show a summary per file
File Description
.github/aw/test-coverage.md Adds fallback coverage guidance and an example network.allowed configuration.
.github/aw/create-agentic-workflow.md Strengthens PR scoping guidance for backend contract reviews and adds a compact backend-review checklist.

Copilot's findings

Tip

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

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

Comment on lines +48 to +52
- infer the repository ecosystem from project files before running fallback coverage
- configure `network.allowed` to include `defaults` plus the inferred ecosystem(s) (for example `node`, `python`, `go`)
- never run fallback coverage with `network: defaults` alone

Example fallback network config:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants