Repository navigation
Restrict GitHub workflows to microsoft/aspire - #20722
Conversation
Co-authored-by: radical <1472+radical@users.noreply.github.com>
Co-authored-by: radical <1472+radical@users.noreply.github.com>
Co-authored-by: radical <1472+radical@users.noreply.github.com>
Co-authored-by: radical <1472+radical@users.noreply.github.com>
Co-authored-by: radical <1472+radical@users.noreply.github.com>
Co-authored-by: radical <1472+radical@users.noreply.github.com>
|
Copilot do we really need this on every job? Shouldn't it be on every workflow? |
GitHub Actions doesn’t support a workflow-level |
|
Copilot Don't modify the labeler workflows, those are being used as-is. |
Co-authored-by: radical <1472+radical@users.noreply.github.com>
Reverted all labeler workflow changes to their pre-PR state in |
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20722Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20722" |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: radical <1472+radical@users.noreply.github.com>
…flows-to-microsoft-aspire # Conflicts: # .github/workflows/milestone-changelog.lock.yml Co-authored-by: radical <1472+radical@users.noreply.github.com>
Five workflow tests assert literal YAML conditions rather than behavior. Changing the repository guards requires rewriting those expectations without demonstrating that the workflows run correctly. Remove those five tests. Retain behavioral Node harness tests, untouched assertions, and shared helpers. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 401f795f-42c1-4ff5-929a-2b40840c86a6
This comment has been minimized.
This comment has been minimized.
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
Bring the PR up to current main while preserving its workflow repository guards. The merge resolves cleanly without additional product changes. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 74ccba9f-30ce-4acd-ab34-cde9555081fb
Tests selectorSelects the full PR test matrix + all PR-gated jobs (ALL) — a rule matching '.github/workflows/run-tests.yml' selects ALL Selection computed for commit |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
Description
GitHub Actions jobs should run only in
microsoft/aspire, but repository-owner checks also allow other repositories under the same organization, and some jobs have no repository guard.Use exact repository checks across direct and reusable workflows, including agentic workflow sources and generated locks. Narrow
GITHUB_TOKENpermissions on test workflows and update the related CI documentation.Remove five tests that asserted literal YAML strings and were changed only to match the new repository conditions. These expectations duplicate configuration rather than exercise workflow behavior. Existing behavioral Node harness tests remain; untouched YAML assertions are outside this cleanup.
Validation on macOS arm64: the following command passed all 41 remaining tests in the three affected classes (0 failed, 0 skipped):
git --no-pager diff --checkalso passed. These local tests do not validate GitHub Actions repository gating end to end.Checklist
<remarks />and<code />elements on your triple slash comments?