Group issue creation by target-framework moniker (TFM) #39
Assignees
Labels
enhancement
New feature or request
Comments
This was referenced Apr 6, 2021
IEvangelist
added a commit
to dotnet/dotnet-api-docs
that referenced
this issue
Apr 7, 2021
Part of issue dotnet/versionsweeper#39 and dotnet/versionsweeper#40
IEvangelist
added a commit
to dotnet/samples
that referenced
this issue
Apr 7, 2021
Part of issue dotnet/versionsweeper#39 and dotnet/versionsweeper#40
IEvangelist
added a commit
to dotnet/docs
that referenced
this issue
Apr 7, 2021
Part of issue dotnet/versionsweeper#39 and dotnet/versionsweeper#40
This was referenced Apr 7, 2021
IEvangelist
added a commit
to dotnet/docs
that referenced
this issue
Apr 7, 2021
IEvangelist
added a commit
to dotnet/samples
that referenced
this issue
Apr 7, 2021
IEvangelist
added a commit
to dotnet/dotnet-api-docs
that referenced
this issue
Apr 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There a large number of issues being created, which feels like spam. For example, see dotnet/dotnet-api-docs.
We need to reduce the number of issues created by automation, let's update the .NET version sweeper tool to group issues by TFM. When to tool detects violations (non-ignored TFMs that are out of support), it will group them together into a single issue. As an example, when there are multiple projects targeting
netcoreapp1.0it would group all of these projects into a checklist on the same issue, rather than an issue per project.The text was updated successfully, but these errors were encountered: