Not Triaged labeling of issues

[guardrex]

@adegeo @Rick-Anderson @wadepickett @tdykstra ...

Please take a look at an issue that I opened this morning at ...

#34870

My GH Action correctly removed the Not Triaged label, but then the dotnet-policy-service re-added it per ...

https://github.com/dotnet/AspNetCore.Docs/blob/main/.github/policies/issueManagement-notTriaged.yml

The Blazor/Blazor Hybrid issues shouldn't have the Not Triaged label applied.

You might want to change the rule in a general way so that it only places the Not Triaged label for issues that don't have a project assigned (and/or perhaps with at least one assignee). This is a docs team decision in the general case, which is why I pinged everyone to take a look at this.

If the team doesn't want a general rule change that would apply to all issues, could we at least avoid applying the Not Triaged label to the Blazor/Blazor Hybrid issues? It could be done using any of the following criteria.

Don't apply the Not Triaged label to issues where (any one of these will do) ...

• guardrex is assigned.
• The issue is on the Blazor.Docs project (Blazor.Docs) or on the Blazor Hybrid project (Blazor Hybrid).
• The issue has either the Blazor label or Blazor Hybrid label applied.
• The issue has either the blazor/sub-svc label or blazor-hybrid/sub-svc label applied.

[Rick-Anderson]

I filed https://github.com/GitOps-microsoft/docs/issues/290 because dotnet-policy-service closing issues it shouldn't

[guardrex]

I haven't seen that happen yet with a Blazor issue.

Otherwise, I'm still having trouble using GH docs. Either they're terrible or I'm terrible! 😆 I often can't find the most basic examples. All we need here is a simple label filter, and nothing I tried worked.

[guardrex]

Seems to be running OK now. The Not Triaged label is added. Then, the GH Action removes it 🔪. Closing now!

[guardrex]

Re-opening this due to ...

#34927

... where it just happened again. 😈

[adegeo]

I filed https://github.com/GitOps-microsoft/docs/issues/290 because dotnet-policy-service closing issues it shouldn't

@Rick-Anderson this is happening because of the spam detection rule which looks for issues created with a default description. This is what the majority of bots do, they open issues with a title but leave the description field set to the default [describe your issue] (or whatever it is) text.

When you create issues, put something (even blank would work, I think) in the description. If you want to just manage the spam by hand, you can delete the rule.

[adegeo]

@guardrex It seems having a condition where the assignee isn't guardrex would work in modifying the behavior. I can do that real fast.

[adegeo]

#34933

[guardrex]

Fixed (temporarily until we drop Actions for policies) by #34933.