Technical Workflows#
A process workflow defines what must be done and who is responsible. A technical workflow explains how to do it with tools such as GitHub and an AI-assisted editor. It does not add process requirements.
For example, Create/Maintain Platform Ma... uses PR Authoring to prepare a change and PR Review to check and approve it.
Rules for AI Assistance#
The existing Usage of Generative AI applies:
The author understands and takes responsibility for every submitted change.
AI suggestions do not replace human review or reduce its scope.
Only humans approve. AI agents and bots must not merge PRs or push directly to protected branches.
Disclose AI assistance in commits, PR text, and comments as the guideline requires.
Share only information permitted for the selected AI service. Use existing templates, checklists, and reviewed instructions; do not ask AI to invent missing decisions or evidence.
AI use is optional. If it is unavailable or its review is incomplete, say so in the PR and carry out the full human review. Keep decisions and review comments in the existing PR, not only in a chat. No additional report is required here.
Existing Responsibilities Still Apply#
Use the approving roles defined by the process workflow as well as the required human committer approval. Having permission to merge does not by itself fulfill the process’s approval responsibility.
Ordinary PR review is not the formal inspection described by Work product Inspections Co.... Where that inspection is required, follow its existing rules.
Tool evaluation remains part of Evaluate Tool and Update To.... The concept and tool-management guidance explain the AI-specific considerations.