Update CI workflow owner guards and repo references from dotnet to microsoft (#15452)

* Update all dotnet/aspire references to microsoft/aspire

Updated all GitHub Actions workflow owner guards from
repository_owner == 'dotnet' to repository_owner == 'microsoft'
across 24 workflow files.

Replaced all dotnet/aspire repository references with microsoft/aspire
across 288 files including workflows, scripts, tests, READMEs, source
code, templates, and documentation. Preserved aka.ms short links
pointing to dotnet/aspire as those are external redirects.

Fixed SigstoreNpmProvenanceCheckerTests expectedOwner to match the
updated URL.

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

* Use GitHub App token for PR creation in all workflows

The microsoft org disables GITHUB_TOKEN from creating PRs. This updates
all 10 workflows that create PRs to use a GitHub App installation token
(via actions/create-github-app-token) instead.

- 9 workflows: add app token step, pass to existing PR creation logic
- backport: rewrite locally (arcade reusable workflow doesn't accept
  custom tokens), filed dotnet/arcade#16585 for upstream support
- release-github-tasks: also fix head: -> branch: bug in PR creation

Replicates changes from microsoft/aspire-internal-reorg-temp#10.

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

* Revert bicep file changes

These are generated files that should not be modified directly.
The dotnet/aspire issue URLs embedded in the SQL deployment scripts
within these bicep files are correct as-is.

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

---------

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

Author: joperezr

.github/ISSUE_TEMPLATE/10_bug_report.yml

@@ -10,11 +10,11 @@ body:
         Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting **non-security** bugs and feature requests.
 
         If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead email your issue details to secure@microsoft.com. Your report may be eligible for our [bug bounty](https://www.microsoft.com/msrc/bounty-dot-net-core) but ONLY if it is reported through email.
-        For other types of questions, consider using [Discussions](https://github.com/dotnet/aspire/discussions).
+        For other types of questions, consider using [Discussions](https://github.com/microsoft/aspire/discussions).
   - type: checkboxes
     attributes:
       label: Is there an existing issue for this?
-      description: Please search to see if an issue already exists for the bug you encountered ([aspire/issues](https://github.com/dotnet/aspire/issues)). More information on our issue management policies is available [here](https://aka.ms/aspnet/issue-policies).
+      description: Please search to see if an issue already exists for the bug you encountered ([aspire/issues](https://github.com/microsoft/aspire/issues)). More information on our issue management policies is available [here](https://aka.ms/aspnet/issue-policies).
       options:
         - label: I have searched the existing issues
           required: true

.github/ISSUE_TEMPLATE/20_feature-request.yml

@@ -9,7 +9,7 @@ body:
   - type: checkboxes
     attributes:
       label: Is there an existing issue for this?
-      description: Please search to see if an issue already exists for the feature you are requesting. (https://github.com/dotnet/aspire/issues).
+      description: Please search to see if an issue already exists for the feature you are requesting. (https://github.com/microsoft/aspire/issues).
       options:
         - label: I have searched the existing issues
           required: true

.github/ISSUE_TEMPLATE/40_blocking_clean_ci.yml

@@ -11,7 +11,7 @@ body:
   - type: checkboxes
     attributes:
       label: Is there an existing issue for this?
-      description: Please search to see if an issue already exists for the failure you encountered ([aspire/issues](https://github.com/dotnet/aspire/issues)). More information on our issue management policies is available [here](https://aka.ms/aspnet/issue-policies).
+      description: Please search to see if an issue already exists for the failure you encountered ([aspire/issues](https://github.com/microsoft/aspire/issues)). More information on our issue management policies is available [here](https://aka.ms/aspnet/issue-policies).
       options:
         - label: I have searched the existing issues
           required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: true
 contact_links:
   - name: Aspire Discussions
-    url: https://github.com/dotnet/aspire/discussions
+    url: https://github.com/microsoft/aspire/discussions
     about: For other types of questions, consider using Discussions.
   - name: Issue Management Policies
     url: https://aka.ms/aspnet/issue-policies

.github/instructions/client-readme.instructions.md

@@ -212,16 +212,16 @@ builder.Add{Technology}{Client}("{connectionName}");
 ## Additional documentation
 
 * {Link to official technology documentation}
-* https://github.com/dotnet/aspire/tree/main/src/Components/README.md
+* https://github.com/microsoft/aspire/tree/main/src/Components/README.md
 
 ## Feedback & contributing
 
-https://github.com/dotnet/aspire
+https://github.com/microsoft/aspire
 ```
 
 **Guidelines:**
 - Always include a link to the official technology/SDK documentation
-- Always include the link to Aspire Components README: `https://github.com/dotnet/aspire/tree/main/src/Components/README.md`
+- Always include the link to Aspire Components README: `https://github.com/microsoft/aspire/tree/main/src/Components/README.md`
 - Use bulleted list format with `*` prefix
 - "Feedback & contributing" section should be separate with just the GitHub link
 
@@ -354,11 +354,11 @@ builder.AddNpgsqlDataSource("postgresdb");
 ## Additional documentation
 
 * https://www.npgsql.org/doc/basic-usage.html
-* https://github.com/dotnet/aspire/tree/main/src/Components/README.md
+* https://github.com/microsoft/aspire/tree/main/src/Components/README.md
 
 ## Feedback & contributing
 
-https://github.com/dotnet/aspire
+https://github.com/microsoft/aspire
 
 _*Postgres*, *PostgreSQL* and the *Slonik Logo* are trademarks or registered trademarks of the *PostgreSQL Community Association of Canada*, and used with their permission._
 ```
@@ -405,7 +405,7 @@ Settings classes follow consistent naming:
 - ❌ Don't omit prerequisites
 - ❌ Don't forget to show the dependency injection example
 - ❌ Don't use inconsistent configuration key naming
-- ❌ Don't forget the link to `https://github.com/dotnet/aspire/tree/main/src/Components/README.md`
+- ❌ Don't forget the link to `https://github.com/microsoft/aspire/tree/main/src/Components/README.md`
 - ❌ Don't explain health checks, telemetry, or observability in detail (they're automatically enabled)
 - ❌ Don't forget trademark notices when applicable
 

.github/instructions/hosting-readme.instructions.md

@@ -133,7 +133,7 @@ configured. See [Local Azure Provisioning](https://aspire.dev/integrations/cloud
 ```markdown
 ## Feedback & contributing
 
-https://github.com/dotnet/aspire
+https://github.com/microsoft/aspire
 ```
 
 **Guidelines:**
@@ -195,7 +195,7 @@ https://aspire.dev/integrations/databases/postgresql-extensions/
 
 ## Feedback & contributing
 
-https://github.com/dotnet/aspire
+https://github.com/microsoft/aspire
 
 _*Postgres*, *PostgreSQL* and the *Slonik Logo* are trademarks or registered trademarks of the *PostgreSQL Community Association of Canada*, and used with their permission._
 ````

.github/skills/ci-test-failures/SKILL.md

@@ -20,15 +20,15 @@ When CI tests fail, use the `DownloadFailingJobLogs.cs` tool to automatically do
 Get the run ID from the GitHub Actions URL or use the `gh` CLI:
 
 ```bash
-# From URL: https://github.com/dotnet/aspire/actions/runs/19846215629
+# From URL: https://github.com/microsoft/aspire/actions/runs/19846215629
 #                                                        ^^^^^^^^^^
 #                                                        run ID
 
 # Or find the latest run on a branch
-gh run list --repo dotnet/aspire --branch <branch-name> --limit 1 --json databaseId --jq '.[0].databaseId'
+gh run list --repo microsoft/aspire --branch <branch-name> --limit 1 --json databaseId --jq '.[0].databaseId'
 
 # Or for a PR
-gh pr checks <pr-number> --repo dotnet/aspire
+gh pr checks <pr-number> --repo microsoft/aspire
 ```
 
 ### Step 2: Run the Tool
@@ -66,10 +66,10 @@ The tool creates files in your current directory:
 
 ```bash
 # 1. Check failed jobs on a PR
-gh pr checks 14105 --repo dotnet/aspire 2>&1 | Where-Object { $_ -match "fail" }
+gh pr checks 14105 --repo microsoft/aspire 2>&1 | Where-Object { $_ -match "fail" }
 
 # 2. Get the run ID
-$runId = gh run list --repo dotnet/aspire --branch davidfowl/my-branch --limit 1 --json databaseId --jq '.[0].databaseId'
+$runId = gh run list --repo microsoft/aspire --branch davidfowl/my-branch --limit 1 --json databaseId --jq '.[0].databaseId'
 
 # 3. Download failure logs
 cd tools/scripts
@@ -93,7 +93,7 @@ The tool prints a summary for each failed job:
 === Failed Job 1/1 ===
 Name: Tests / Integrations macos (Hosting.Azure) / Hosting.Azure (macos-latest)
 ID: 56864254427
-URL: https://github.com/dotnet/aspire/actions/runs/19846215629/job/56864254427
+URL: https://github.com/microsoft/aspire/actions/runs/19846215629/job/56864254427
 Downloading job logs...
 Saved job logs to: failed_job_0_Tests___Integrations_macos__Hosting_Azure____Hosting_Azure__macos-latest_.log
 
@@ -142,7 +142,7 @@ Get-Content "failed_job_*.log" | Select-String -Pattern "timeout|timed out|Timeo
 Sometimes job logs aren't available (404). Use annotations instead:
 
 ```bash
-gh api repos/dotnet/aspire/check-runs/<job-id>/annotations
+gh api repos/microsoft/aspire/check-runs/<job-id>/annotations
 ```
 
 This returns structured error information even when full logs aren't downloadable.
@@ -155,7 +155,7 @@ This returns structured error information even when full logs aren't downloadabl
 
 **Diagnosis:**
 ```powershell
-gh api repos/dotnet/aspire/check-runs/<job-id>/annotations 2>&1
+gh api repos/microsoft/aspire/check-runs/<job-id>/annotations 2>&1
 ```
 
 **Common fixes:**
@@ -268,7 +268,7 @@ rm -rf tools/scripts/artifact_*
 
 - .NET 10 SDK or later
 - GitHub CLI (`gh`) installed and authenticated
-- Access to the dotnet/aspire repository
+- Access to the microsoft/aspire repository
 
 ## See Also
 

.github/skills/cli-e2e-testing/SKILL.md

@@ -524,7 +524,7 @@ gh run list --branch $(git branch --show-current) --workflow CI --limit 5
 # Get the run ID from the output or use:
 RUN_ID=$(gh run list --branch $(git branch --show-current) --workflow CI --limit 1 --json databaseId --jq '.[0].databaseId')
 echo "Run ID: $RUN_ID"
-echo "URL: https://github.com/dotnet/aspire/actions/runs/$RUN_ID"
+echo "URL: https://github.com/microsoft/aspire/actions/runs/$RUN_ID"
 ```
 
 ### Step 2: Find CLI E2E Test Artifacts
@@ -538,7 +538,7 @@ Artifact names follow the pattern: `logs-<TestClass>-ubuntu-latest`
 gh run view $RUN_ID --json jobs --jq '.jobs[] | select(.name | test("Cli E2E")) | {name, conclusion}'
 
 # List available CLI E2E artifacts
-gh api --paginate "repos/dotnet/aspire/actions/runs/$RUN_ID/artifacts" \
+gh api --paginate "repos/microsoft/aspire/actions/runs/$RUN_ID/artifacts" \
   --jq '.artifacts[].name' | grep -i "smoke"
 ```
 

.github/skills/dependency-update/SKILL.md

@@ -3,7 +3,7 @@ name: dependency-update
 description: Guides dependency version updates by checking nuget.org for latest versions, triggering the dotnet-migrate-package Azure DevOps pipeline, and monitoring runs. Use this when asked to update external NuGet dependencies.
 ---
 
-You are a specialized dependency update agent for the dotnet/aspire repository. Your primary function is to help update external NuGet package dependencies by finding latest versions, assessing changes, triggering the internal mirroring pipeline, and updating `Directory.Packages.props`.
+You are a specialized dependency update agent for the microsoft/aspire repository. Your primary function is to help update external NuGet package dependencies by finding latest versions, assessing changes, triggering the internal mirroring pipeline, and updating `Directory.Packages.props`.
 
 ## Background