[github-actions]

Documentation Updates - 2026-11-04

Clarify that every push_to_pull_request_branch call requires message, even when changes are already committed. The argument has no default, is not inferred from git, and does not replace existing commit messages.

Features Documented

• Required PR branch-push message argument, following #74740 and #74710.
• One reference page changed; no workflow examples or runtime behavior changed.

Review details and skipped issues

Review Scope

Screened accessible merged-PR results and commits dated November 3–4, plus open documentation issues and recently closed documentation issues. The PR search returned 95 matches, of which 45 were withheld by the integrity policy. Cookie issue results and some other issue/PR details were also withheld; these were not bypassed or independently recovered. This is a partial review of accessible material.

The telemetry partial-success, signal-specific protocol, and prompt-expression validation changes already have reference documentation. Checked the new message wording against the checked-out safe-output tool schema. Steering issue #74827 had no comments when checked.

Skipped Issues

• Add SOC-2 compliance patterns doc page #41746 — already addressed by reference/compliance-patterns.md, linked from enterprise configuration.
• Provider-based authentication for Claude, Copilot, Codex. #16498 — supported Claude authentication and unsupported subscription OAuth tokens are already documented; broader provider implementation work is outside this documentation edit.
• OWASP Agentic Top 10 compliance evaluation: gap analysis across gh-aw, firewall, and mcpg #28770 — broad security assessment and proposed runtime changes require a separate technical review; no unsupported compliance claims added.
• 🔍 Multi-Device Docs Testing Report - 2026-11-01 #73716 and 🔍 Multi-Device Docs Testing Report - 2026-10-31 #73430 — site-build/UI: needs Astro/site-build agent.
• [cli-consistency] CLI Consistency Issues - 2026-11-03 #74529 — CLI shorthand conflict addressed by Remove the conflicting -l shorthand from project new #74561; no content gap identified.
• [cli-consistency] CLI Consistency Issues - 2026-10-29 #72983, [cli-consistency] CLI Consistency Issues - 2026-10-28 #72701, and [cli-consistency] CLI Consistency Issues - 2026-10-27 #72447 — sampled reported content gaps are already addressed: audit lists outcomes, command options list --pr-message, work-queue points to subcommand help, and --read-only is described as hidden. Remaining CLI behavior requests are outside scope.
• [workflow-style] Normalize report formatting for non-compliant workflows #72980 — workflow prompt formatting is outside this content-reference update.
• Integrity-filtered issues could not be assessed.

Validation

• git diff --check passed; final working tree is clean.
• make agent-report-progress was attempted and stopped at the Go build: downloading Go 1.27.3 failed TLS certificate validation for proxy.golang.org. Tests were not reached. No TLS settings or environment protections were changed.

Notes

The legacy .github/instructions/documentation.instructions.md path is absent; the current .github/skills/documentation/SKILL.md supplied the documentation conventions.

AI dictionary alignment summary: reviewed the existing term tool call against the supplied dictionary summary; retained that term and repository-specific safe-output names. No terminology conflicts or new AI terms.

Next Actions

Review the concise reference clarification and run the repository validation gate in CI with the required Go toolchain available.

Generated by 📝 Daily Documentation Updater · codex · gpt60 · ~230 AIC · ⌖ ~95 AIC · ⊞ 19.6K · ◷

• expires on Nov 5, 2026, 2:47 AM UTC-08:00

[Copilot]

🟡 Changes recommended

The reference documentation overstates commit-message preservation by omitting the default signed-commit merge-range squash exception.

1 open issue

• Document that signed commits squash ranges into one commit · New

What changed in this PR

This documentation-only pull request clarifies that every push_to_pull_request_branch call requires an explicit message argument, including when changes are already committed. It does not change runtime behavior or workflow examples.

Changes:

• Documents that message is required, has no default, and is not inferred from Git.
• Clarifies that the argument does not replace existing commit messages.
• Adds a qualification for signed pushes containing merge commits, where local history may be squashed.

File	Summary
docs/​src/​content/​docs/​reference/​safe-outputs-pull-requests.md	Adds the required-message clarification and commit-message behavior guidance. Nit (2 votes): qualify the preservation statement to account for merge commits being squashed when signed commits are enabled.

_{Review effort: Lite (auto)}