Skip to content

[awf-feature-surfacing] Surface allowed-teams mentions option in agentic docs (.github/aw/safe-outputs-runtime.md) #40397

@github-actions

Description

@github-actions

Summary

PR #40368 added a new allowed-teams option to the safe-outputs.mentions configuration, letting workflows allow all members of named GitHub teams to be @mentioned without enumerating individual usernames. The feature is implemented and validated, but it is not surfaced in the agentic-facing docs under .github/aw/ that agents read when authoring/editing workflows. As a result, an agent generating a workflow will not discover this capability.

Feature

  • Feature ID: awf-feat-mentions-allowed-teams
  • Schema key: safe-outputs.mentions.allowed-teams (array of team-slug or org/team-slug)
  • Team members are resolved from the GitHub API at runtime; bots excluded. Requires read:org scope (not in default GITHUB_TOKEN).
Evidence
  • Commit: b56f9a6 — feat(safe-outputs): add allowed-teams to mentions configuration (feat(safe-outputs): add allowed-teams to mentions configuration #40368)
  • Schema: pkg/parser/schemas/main_workflow_schema.json (allowed-teams at line ~10224)
  • Compiler: pkg/workflow/safe_outputs_messages_config.go, pkg/workflow/safe_outputs_config.go, pkg/workflow/compiler_types.go
  • ADR: docs/adr/40368-resolve-mentions-via-team-membership.md

Current surfacing status

Surface Status
JSON schema ✅ documented (incl. read:org scope note)
docs/src/content/docs/reference/safe-outputs.md ✅ full prose + example + scope warning
docs/src/content/docs/reference/frontmatter-full.md ✅ example entry
ADR 40368-...md ✅ present
.github/aw/safe-outputs-runtime.md missing — the mentions: object example/prose lists only allow-team-members, allow-context, allowed, max

Follow-up tasks

  1. [High] Add allowed-teams to the mentions: object example and prose in .github/aw/safe-outputs-runtime.md (around lines 135–149), including the read:org scope caveat and the org/team-slug vs bare team-slug resolution rule.
  2. [Low] Cross-check other agentic docs that mention mentions: (e.g. .github/aw/report.md, .github/aw/messages.md) for whether a pointer to allowed-teams is warranted.
  3. [Low] Confirm a frontmatter example or pattern doc shows a realistic allowed-teams usage so agents have a copyable snippet.

Notes

  • No duplicate issue exists for this feature.
  • User-facing reference docs already cover the feature; the gap is specifically the agentic .github/aw/ context surface.

Generated by 🧭 Daily AWF Spec Compiler Surfacing Review · 82.4 AIC · ⌖ 12.2 AIC · ⊞ 5.2K ·

  • expires on Jun 26, 2026, 2:35 PM UTC-08:00

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions