ci: delete unused add-remove-label-check-suites workflow#35450
Merged
jfversluis merged 1 commit intoMay 19, 2026
Conversation
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 35450Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 35450" |
Contributor
|
Hey there @@arpitjain099! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
PureWeen
requested changes
May 14, 2026
PureWeen
left a comment
Member
There was a problem hiding this comment.
AFAICT we aren't using this workflow anymore
Can you update this PR to just delete it?
This was referenced May 15, 2026
Contributor
Author
|
Hi @PureWeen, force-pushed the branch: the PR now just deletes |
32b1eb7 to
743a4ea
Compare
PureWeen
added a commit
that referenced
this pull request
May 17, 2026
Three findings from a multi-model adversarial review (claude-opus-4.6 + claude-sonnet-4.6 + gpt-5.3-codex with disputed-finding follow-ups): 1. **(3/3) Broken eval: 'Tooling area - CI workflow changes'** The scenario at lines 69-77 asserted `area-tooling` for PR #35450, but PR #35450 only deletes `.github/workflows/add-remove-label-check-suites.yml` and its real applied label is `area-infrastructure`. The previous commit added a rule that explicitly says workflow-only PRs should get `area-infrastructure` (not `area-tooling`), making this eval scenario contradict the very rule it was supposed to validate. Renamed to 'Infrastructure area - CI workflow file deletion' and updated the assertions to expect `area-infrastructure` and NOT `area-tooling`. 2. **(2/3) Noop regex matched too loosely** The patterns at lines 100 and 181 included bare `skip` and bare `no action`, which would match agent commentary like 'applied area-infrastructure. This requires no action from the maintainer.' — producing a false-positive noop signal even when the agent applied labels. Replaced bare `skip` → `skip.+label` (line 181 only — line 100 already had this) and bare `no action` → `no.+action.+(needed|required|appropriate|necessary)` on both lines. Verified against 5 legitimate noop phrasings and 2 false-positive scenarios: the tightened patterns reject the false positives while still matching all legitimate noop output. 3. **(2/3) 'touching only' qualifier ambiguous for mixed PRs** The `area-infrastructure` rule said 'PRs touching only ... infra files → area-infrastructure', which didn't address PRs that mix infra and product-code changes. An empirical check showed ~17% of recent PRs in dotnet/maui mix infra+src paths, but `area-infrastructure` is currently applied sparingly (mostly to infra-primary work, not every PR that touches an infra file). Added a tiebreaker: if the PR is dominated by infra changes with incidental product edits, apply `area-infrastructure` alongside any relevant product area label; if the product change is the focus and infra is incidental, prefer the product area label and omit `area-infrastructure`. Discarded findings (low confidence after consensus rounds): - Token-in-.git/config persistence (security): gh-aw framework concern, not introduced by this PR; cleanup runs before the agent executes; agent token is read-only scoped. - Hardcoded PR/issue numbers in evals: known eval-design trade-off. - `output_not_contains: 'platform/'` brittle: substring is acceptable given that all platform/* labels share the prefix. - Dependency-bump noop timing edge case: rule is correct as stated. - Missing iOS/Windows handler subdirectory patterns: existing extension patterns cover them in practice. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
@dotnet-policy-service agree |
Contributor
Author
|
@PureWeen I deleted the workflow as asked |
This was referenced May 18, 2026
kubaflo
approved these changes
May 19, 2026
Contributor
|
@jfversluis can you merge this? |
jfversluis
approved these changes
May 19, 2026
This was referenced May 20, 2026
This was referenced May 21, 2026
Draft
devanathan-vaithiyanathan
pushed a commit
to devanathan-vaithiyanathan/maui
that referenced
this pull request
Jun 1, 2026
Per @PureWeen's review on the original PR, this workflow is no longer in use. Replacing the permissions-block edit with a straight deletion. No functional change beyond removing the unused trigger. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
4 tasks
devanathan-vaithiyanathan
pushed a commit
to devanathan-vaithiyanathan/maui
that referenced
this pull request
Jun 5, 2026
Per @PureWeen's review on the original PR, this workflow is no longer in use. Replacing the permissions-block edit with a straight deletion. No functional change beyond removing the unused trigger. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
This was referenced Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per @PureWeen's review on the original PR, this workflow is no longer in use. Replacing the permissions-block edit with a straight deletion.
No functional change beyond removing the unused trigger.