docs: link RELEASING runbook + clean up legacy ADO release doc

Phase 1 finish + Phase 2 of the release-strategy work.

- README.md: add 'see RELEASING.md' line under 'Changes and versioning'.
- CONTRIBUTING.md: replace stale 'docs/release.md' link with link to
  RELEASING.md.
- docs/release.md: replace ADO-flavored release doc (referenced obsolete
  Azure DevOps build numbers like 0.2.0-B2103003) with a stub pointing
  to RELEASING.md.
- docs/publish/devops-wiki.md: page was a 'Coming soon' stub; expand it
  with both Azure Pipelines and GitHub Actions tabs covering the same
  scenario, matching the convention used elsewhere in the docs.
- MONOREPO_MIGRATION.md: under 'Future Subtree Updates', add a callout
  reminding maintainers to delete upstream .azure-pipelines/ and nested
  .github/ directories after each subtree pull (the monorepo uses GH
  Actions only at the repo root).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: vicperdana

CONTRIBUTING.md

@@ -57,7 +57,8 @@ Check out the links below to get started.
 
 ### Release Process
 
-Refer to [release process](docs/release.md)
+See [RELEASING.md](RELEASING.md) for the full release runbook covering all three packages
+(PSDocs, PSDocs.Azure, VS Code extension), tag conventions, and the pre-release flow.
 
 ## Thank You!
 

MONOREPO_MIGRATION.md

@@ -145,6 +145,20 @@ git subtree pull --prefix=packages/psdocs https://github.com/microsoft/PSDocs.gi
 git subtree pull --prefix=packages/vscode-extension https://github.com/microsoft/PSDocs-vscode.git main --squash
 ```
 
+> **After any subtree pull**, audit the result and remove anything we don't
+> want to inherit from upstream:
+>
+> - `packages/*/.azure-pipelines/` and `packages/*/azure-pipelines*.yaml` —
+>   the monorepo uses GitHub Actions (`/.github/workflows/`); upstream ADO
+>   pipelines are not active here and should be deleted to avoid confusion.
+> - `packages/*/.github/workflows/` — workflows nested inside packages do
+>   not run on GitHub. Either delete them or, if a workflow is genuinely
+>   wanted, move and adapt it under root `.github/workflows/` with
+>   appropriate path filters.
+> - Any upstream `.github/dependabot.yml` / `.github/CODEOWNERS` etc. —
+>   monorepo policy lives at the repo root and should not be shadowed by
+>   per-package copies.
+
 ## Workflow Migration
 
 The following legacy workflows were removed as part of the monorepo migration, replaced by new workflows with path-based filtering:

README.md

@@ -339,6 +339,8 @@ For a list of module changes please see the [change log](CHANGELOG.md).
 > Pre-release versions should be considered experimental.
 > Modules and change log details for pre-releases will be removed as standard releases are made available.
 
+For maintainers cutting a release, see [RELEASING.md](RELEASING.md).
+
 ## Contributing
 
 This project welcomes contributions and suggestions.

docs/publish/devops-wiki.md

@@ -1,8 +1,35 @@
-# Publish to Azure DevOps Wiki
+# Publish to a wiki
 
-Markdown generated with PSDocs for Azure can be published as wiki content for viewing with Azure DevOps.
+Markdown generated with PSDocs for Azure can be published as wiki content for
+viewing on Azure DevOps Wiki, GitHub Wiki, or any other Markdown-friendly
+documentation host.
 
 !!! Abstract
-    This topic covers using a pipeline to publish markdown generated by PSDocs for Azure into an Azure DevOps Wiki.
+    This topic covers using a pipeline to publish markdown generated by
+    PSDocs for Azure to either an Azure DevOps Wiki or a GitHub Wiki / GitHub
+    Pages site.
 
-_Coming soon_.
+_Coming soon_ — detailed pipeline samples for both options.
+
+In the meantime, the general approach is:
+
+=== "Azure Pipelines"
+
+    1. Run `Invoke-PSDocument` against your templates in a build job, writing
+       Markdown to a known output directory.
+    2. Publish the output as a pipeline artifact.
+    3. In a release stage, `git clone` the wiki repo (each Azure DevOps Wiki
+       is backed by a Git repository), copy the artifact's Markdown into the
+       wiki repo, commit, and push.
+
+=== "GitHub Actions"
+
+    1. Run `Invoke-PSDocument` against your templates in a workflow job,
+       writing Markdown to a known output directory.
+    2. Either:
+        - Push the Markdown to the repository's GitHub Wiki (the `*.wiki.git`
+          repo) using a workflow such as
+          [`Andrew-Chen-Wang/github-wiki-action`](https://github.com/Andrew-Chen-Wang/github-wiki-action), **or**
+        - Publish the Markdown to GitHub Pages using the standard
+          [`actions/deploy-pages`](https://github.com/actions/deploy-pages)
+          flow with a static-site generator like MkDocs or Jekyll.

docs/release.md

@@ -1,13 +1,15 @@
-# Release process for PSDocs for Azure
-
-The following sections describe the process for making a new release.
-
-- Update [CHANGELOG](../CHANGELOG.md) with all changes since the last release (including all pre-release versions)
-- Submit a Pull Request for review
-- Navigate to [Releases](https://github.com/Azure/PSDocs.Azure/releases) and select **Draft a new release**
-- [SemVer](https://semver.org/) is used to version the releases.  To use the correct release/tag the following options are used:
-  - A stable release: increment from the previous release *e.g. v0.2.0*
-  - A pre-release: select the **This is a pre-release** option and select the build version from the previous build in Azure DevOps Pipelines.  This version can be found from previous build run. *E.g.,  for the recent Pull Request go to Pull Request -> Checks -> Analyze -> Azure Pipelines -> PSDocs.Azure-CI Build **[#0.2.0-B2103003](https://github.com/Azure/PSDocs.Azure/pull/52/checks?check_run_id=2066087539)***
-  - Wait for the deployment to be released in [PowerShell Gallery](https://www.powershellgallery.com/packages/PSDocs.Azure/)
-- After a successful release, create another PR updating:
-  - [.azure-pipelines/azure-pipelines.yaml](https://github.com/Azure/PSDocs.Azure/blob/main/.azure-pipelines/azure-pipelines.yaml) with the next version increment *e.g. if the newly released version is 0.2.0, set this to `version: '0.3.0'`*
+# Release process
+
+The release process for all packages in this monorepo (PSDocs, PSDocs.Azure,
+VS Code extension) is documented in the repo-root [RELEASING.md][releasing]
+runbook.
+
+That runbook covers:
+
+- One-time setup of GitHub Actions secrets and the `release` environment.
+- Tag conventions per package (stable and preview).
+- Step-by-step instructions for cutting a release.
+- Pre-release flow for both PowerShell Gallery and VS Marketplace.
+- Troubleshooting and rollback.
+
+[releasing]: https://github.com/Azure/PSDocs.Azure/blob/main/RELEASING.md