ado-pr-draft

Draft Azure DevOps pull request descriptions locally by generating markdown files with YAML frontmatter. This approach ensures adherence to style guides and naming conventions without creating actual PRs, allowing you to review content before submission.

Yes, you can enforce PR title conventions and description structure by reading a defined style guide during the drafting process. Scripts validate the generated markdown content to ensure it follows specific frontmatter and description guidelines.

Automate pull request drafting by using scripts to gather branch context and generate formatted markdown files. This creates consistent PR content locally, incorporating style guide rules and validation scripts to prepare descriptions for review.

No, this pull request drafting workflow does not create actual PRs in Azure DevOps. It saves drafted content to a designated local directory as markdown files with specific frontmatter, keeping the review process isolated until you are ready to submit.

Generate markdown files with YAML frontmatter for code review by following a defined workflow that gathers context and applies style guide rules. The process outputs validated local files structured for pull request titles and descriptions.

Limitations of local PR content drafting include its restriction to generating files locally without Azure DevOps API integration for direct submission. It focuses solely on content validation and markdown generation, requiring manual upload for actual PR creation.