Skip to content

Conversation

@dibarbet
Copy link
Member

@dibarbet dibarbet requested a review from a team as a code owner October 24, 2025 21:43
@timheuer
Copy link
Member

Sounds like we may also want to get ahead of this for csdevkit as well? I don't think we have grouping there (but I know there is a separate issue tracking putting grouping in to make more sense)

@dibarbet
Copy link
Member Author

Sounds like we may also want to get ahead of this for csdevkit as well? I don't think we have grouping there (but I know there is a separate issue tracking putting grouping in to make more sense)

Could, but my read is it isn't necessary. Dev Kit only has a single group, and so the one group getting the automatic ms-dotnettools.csdevkit id would not be problematic.

Only would need it if they end up making the id a required field even if there is only a single group (but I suspect that would break a huge number of extensions out there and seems unlikely).

@dibarbet dibarbet merged commit fc30092 into dotnet:main Oct 25, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants