Ricardo Arenas

I think it makes sense that it doesn't fit the pr dev wf epic, but I would be sad if it doesn't fit in the known issues epic, as currently...

I think its own epic makes sense if this isn't straightforward, but given how I'm only asking to expand the search to a new org, and we already have multi...

we're using https://github.com/dotnet/arcade/issues/11239 to track these.

This was me as a way to self-report a bug. We are showing the same queue multiple times in the queue insights information: 

@premun also noticed this. In dotnet/runtime it's getting a bit ridiculous as seen in https://github.com/dotnet/runtime/pull/75609/checks?check_run_id=8351713733 

https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service/pullrequest/26106 should do this

This should deploy during the next rollout.

Do we have any context on why this ask wasn't done before the breaking changes were merged, since it looks like the product teams were fully aware this would cause...

I see the two features that build analysis shows as: * Normal known issues: we know for sure your PR hit this error string from the known issue. * Critical...

This repros locally for me when trying to build the main branch of the repo, which makes me believe it's a build authoring error from the repository. This should be...