Escape the dot in the .NET detection regex used to label issues - #14446
Open
Kumaresan-AI-Engineer wants to merge 1 commit into
Open
Kumaresan-AI-Engineer wants to merge 1 commit into
Kumaresan-AI-Engineer wants to merge 1 commit into
Conversation
The issue labeler tested bodies and titles with /.net/i. The unescaped dot is a
regex wildcard, so any character followed by "net" matched: "internet", "network",
"AF_INET", "Mainnet". Python-only issues were labeled .NET as a result, and the
label title prefix workflow then rewrote their titles with a ".Net:" prefix.
Escaping the dot makes the check match a literal ".net" (".NET", "ASP.NET"), which
is what the comment above it describes. The "dotnet", "C#" and "csharp" checks are
unchanged, so genuine .NET issues that spell it that way are still labeled.
Replaying both regexes over the 98 currently open issues changes the outcome for 6
of them; every change removes a false .NET label and none removes a true one.
Examples still carrying the wrong label: microsoft#14412 ("internet") and microsoft#13974 ("Mainnet").
Kumaresan-AI-Engineer
had a problem deploying
to
github-app-auth
September 13, 2026 17:23 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Kumaresan-AI-Engineer
had a problem deploying
to
github-app-auth
September 13, 2026 17:23 — with
GitHub Actions
Failure
GitHub Actions
Failure
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The focused change has no unresolved blocking issues.
Pull request overview
Escapes the dot in the .NET detection regex so unrelated terms no longer receive the .NET label.
Changes:
- Matches literal
.net. - Preserves existing
dotnet,C#, andcsharpchecks.
File summaries
| File | Description |
|---|---|
.github/workflows/label-issues.yml |
Corrects .NET detection regex. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
The issue labeler tested bodies and titles with /.net/i. The unescaped dot is a regex wildcard, so any character followed by "net" matched: "internet", "network", "AF_INET", "Mainnet". Python-only issues were labeled .NET as a result, and the label title prefix workflow then rewrote their titles with a ".Net:" prefix.
Escaping the dot makes the check match a literal ".net" (".NET", "ASP.NET"), which is what the comment above it describes. The "dotnet", "C#" and "csharp" checks are unchanged, so genuine .NET issues that spell it that way are still labeled.
Replaying both regexes over the 98 currently open issues changes the outcome for 6 of them; every change removes a false .NET label and none removes a true one. Examples still carrying the wrong label: #14412 ("internet") and #13974 ("Mainnet").