Skip to content

[docs] Update glossary - daily scan - #55746

Merged
pelikhan merged 3 commits into
mainfrom
docs/glossary-daily-scan-2026-08-25-8b30cd99842963ee
Aug 25, 2026
Merged

[docs] Update glossary - daily scan#55746
pelikhan merged 3 commits into
mainfrom
docs/glossary-daily-scan-2026-08-25-8b30cd99842963ee

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Daily glossary scan (2026-08-25)

Scanned commits from the last 24 hours and added missing terms to docs/src/content/docs/reference/glossary.md.

Terms added

Terms considered but skipped

  • "Automatic Engine Domain Sets" and "Ecosystem Identifiers" — already adequately covered by the existing Ecosystem Identifiers glossary entry and network.md doc.
  • "Schema-aware edit command" (gh aw edit, Add experimental schema-aware gh aw edit #55475) — feature is still marked experimental with no dedicated public reference page yet; deferred to a future scan once documentation stabilizes.

Validation

  • make build-docs completed successfully (link validation passed, 233 pages built).

AI dictionary alignment summary

  • Terms reviewed against the AI Coding Dictionary: none of the new terms map to generic AI-coding vocabulary; all are gh-aw-specific (grader configuration, safe-output steering, workflow metadata), so no renames were needed.

Generated by 📝 Glossary Maintainer · copilot · auto · 77.8 AIC · ⌖ 13 AIC · ⊞ 18.1K ·

  • expires on Aug 27, 2026, 2:27 AM UTC-08:00

…sues, workflow docs URL

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added documentation Improvements or additions to documentation glossary labels Aug 25, 2026
@gh-aw-bot

Copy link
Copy Markdown
Collaborator

gh-aw-pr-sous-chef
@copilot PR Sous Chef triage: this PR still needs a forward-progress pass before maintainer investigation is likely to be productive.

Please refresh the branch if needed, review the current PR state, and use the pr-finisher skill before handing back for maintainer investigation.

Run: https://github.com/github/gh-aw/actions/runs/32839384382

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 17.3 AIC · ⌖ 8.12 AIC · ⊞ 6.2K ·
Comment /souschef to run again

Copilot AI commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

gh-aw-pr-sous-chef
@copilot PR Sous Chef triage: this PR still needs a forward-progress pass before maintainer investigation is likely to be productive.
...

Ran a forward-progress pass with the pr-finisher skill:

  • Mergeable — branch is up to date with main (origin/main = 012c51f, already an ancestor of HEAD 400dc6d); PR is open, not draft, no conflicts.
  • Reviews — no review threads on the PR (reviewThreads is empty); no unresolved feedback to address.
  • Checks (local) — re-ran make build-docs: 233 pages built, "All internal links are valid". Verified the new entries' link targets exist and anchors resolve (/reference/trace-graders/#operational-value-grader, /reference/safe-outputs-pull-requests/#steering-issues, /reference/frontmatter-full/), and confirmed no duplicate glossary entries for graders/steering/metadata.docs. Go targets are not applicable — this PR touches only docs/src/content/docs/reference/glossary.md (+16 lines).
  • Checks (CI) — only the copilot job is attached to this HEAD; CI on this commit needs a maintainer re-trigger (close/reopen or push) since agent pushes don't start workflows.

Content was re-verified against the source docs (trace-graders.md, safe-outputs-pull-requests.md, frontmatter-full.md) and the section placement is correct (Steering Issue under Security and Outputs, graders and metadata.docs under Advanced Features).

No file changes were needed, so there is no new commit. Hand-off: ready for maintainer review/merge once CI is re-triggered.

Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot AI requested a review from gh-aw-bot August 25, 2026 11:07
Comment on lines +565 to +567
### Steering Issue (`create-pull-request.steer`)

An experimental `create-pull-request` safe-output option that creates a run-scoped issue during the activation job, before the agent starts. Users add comments containing the keyword `steer` while the run is in progress, and the injected prompt instructs the agent to read relevant user-authored comments with the GitHub MCP `issue_read` tool. Enabling `steer: true` requires the GitHub MCP issues toolset and top-level `issues: read` permission; the compiler reports an error instead of adding the permission automatically. On success, the conclusion job closes the steering issue and links the created pull request; on failure, the same issue is retitled and updated with the failure report. `steer` cannot be combined with `safe-outputs.failure-issue-repo`, and no steering issue is created in staged mode. See [Safe Outputs (Pull Requests)](/gh-aw/reference/safe-outputs-pull-requests/#steering-issues).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@copilot remove this entry

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.

Removed the Steering Issue (create-pull-request.steer) entry in cff4bba. make build-docs still passes (233 pages, all internal links valid).

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI requested a review from pelikhan August 25, 2026 13:21
@pelikhan
pelikhan merged commit 9dd0eb7 into main Aug 25, 2026
@pelikhan
pelikhan deleted the docs/glossary-daily-scan-2026-08-25-8b30cd99842963ee branch August 25, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation glossary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants