Split doc generation pipeline into parallel v1.0 and beta stages - #825
Split doc generation pipeline into parallel v1.0 and beta stages#825ramsessanchez wants to merge 2 commits into
Conversation
Adds a -GraphProfileFilter parameter (v1.0/beta/both, default both) to the generation and post-processing scripts so each profile can be generated independently, and splits powershell-docs.yml into two parallel stages (GenerateV1, GenerateBeta) via a new reusable common-templates/generate-docs-steps.yml. Each stage generates a single profile, commits to its own branch, and opens its own PR. Built on top of the mass-deletion, idempotency and encoding fixes from ramsess/revert-generation-changes; StabilizeMsDate is intentionally not included as it was removed on that branch. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 07827a2: ✅ Validation status: passed
For more details, please refer to the build report. |
In the split pipeline each profile stage generates a single profile, so a post-processing step can legitimately produce no changes for that profile. A bare 'git commit' exits 1 ('nothing to commit') and, as the last native command in the step, fails the task even though nothing is wrong. Apply the 'commit only if staged changes exist' guard (already present in CorrectRelatedLinks/UpdateLinks/MsSubserviceUpdate) to the remaining scripts: GenerateMarkDown, EscapeDisallowedHtmlTags, GeneratePermissionsTable, RemoveBoilerPlateCode, RemoveInvalidFullStops, RepairExamplesDescriptionsAndTitle.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit d4725c2: ✅ Validation status: passed
For more details, please refer to the build report. |
1 participant
Splits the weekly reference-docs generation into two independent, parallel stages so v1.0 and beta each produce their own PR.
What changed
azure-pipelines/common-templates/generate-docs-steps.ymlruns the full generation + post-processing pipeline for a single profile.azure-pipelines/powershell-docs.ymlnow defines two parallel stages, GenerateV1 and GenerateBeta (dependsOn: []), each consuming the template withGraphProfileFilter=v1.0/beta, its own branch prefix, PR title, and uniquely-namedMissingExternalDocsartifact.-GraphProfileFilterparameter (v1.0|beta|both, defaultboth) so a run can be scoped to one profile. Authentication docs (v1.0-only) are skipped when generating beta.Base
Stacks on
ramsess/revert-generation-changes(#819) — this PR shows only the split changes on top of the mass-deletion / idempotency / encoding fixes.StabilizeMsDateis intentionally not reintroduced (it was removed on that branch).Redo of #806 on the corrected base.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com