Closed guardrex closed 2 hours ago
Stand by! A green dinosaur ๐ฆ will arrive shortly to assist.
@Rick-Anderson @adegeo @tdykstra @wadepickett ... I ran a few tests, and my test issues were labeled correctly in the base case.
This test was a little weird ... https://github.com/dotnet/AspNetCore.Docs/issues/33897 ... where the issue was closed and then re-opened by Repoman when additional processing checks were run.
I can't seem to repro why labels aren't being added to some of the issues. The question is why didn't Repoman run on https://github.com/dotnet/AspNetCore.Docs/issues/33896 given the processing ...
# New issue opened, add Not Triaged
- labels-add: [":watch: Not Triaged"]
... and ...
# default for doc comment
- check:
- type: metadata-exists
pass:
- labels-add: ["Source - Docs.ms"]
- svc_subsvc_labels: true
Another example is https://github.com/dotnet/AspNetCore.Docs/issues/33873.
Is there a known reason why Repoman has intermittent failures?
Not that it matters for why Repoman isn't running, but I wonder why the default for doc comment
processing with the metadata-exists
check is made? Why not just add labels and execute svc_subsvc_labels
for all opened issues? ...
# New issue opened, add Not Triaged
- labels-add: [":watch: Not Triaged"]
- labels-add: ["Source - Docs.ms"]
- svc_subsvc_labels: true
... and then get rid of that default for doc comment
processing?
I'll close this because this isn't a real issue, but I'm ๐ for any discussion.
Description
This is a test issue.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/data-binding.md
Document ID
3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Article author
@guardrex
Related Issues