Add links in "new issue" flow to other related repos #21841
Conversation
|
Seems like an interesting experiment. It'll be interesting if it works. I will say it's fairly uncommon for us to get misreported issues in this repo. Certainly some issues end up being runtime problems, but we don't get a lot of issues where the author was confused. Still, seems reasonable. Though I don't think I should go ahead an approve new issue management flows a day before leaving 😄 |
.github/ISSUE_TEMPLATE/config.yml
Outdated
| - name: Issue with .NET Core SDK | ||
| url: https://github.com/dotnet/sdk/issues/new/choose | ||
| about: Please open issues with the .NET Core SDK in their repo | ||
| - name: Issue with Entity Framework |
There was a problem hiding this comment.
Should this be Entity Framework Core instead?
Or maybe, we should even have two separate ones for EF and EF Core?
@ajcvickers thoughts?
There was a problem hiding this comment.
I changed to Entity Framework Core. I can add regular EF, if you let me know the URL.
There was a problem hiding this comment.
@danmosemsft Looks good the way it is now.
Pilchie
added
the
feature-platform
|
@mkArtakMSFT should be good to merge now? |
|
@mkArtakMSFT can you merge it? Not sure whether it's polite for me to merge into your repo. |
This .yml adds quick links to other repos below the existing issue template buttons in your new issue flow.
For an example of what this will look like, see https://github.com/danmosemsft/runtime/issues/new/choose (the white buttons)
Note that the flow takes you to the other repos issue template selector (if any) otherwise to their new issue form directly.
We are adding this in dotnet/runtime (dotnet/runtime#36431). Reasoning: it's sometimes confusing which is the correct repo to open an issue in. The goal here is to make it easier to open an issue in the correct repo first time so we need to move fewer issues and they more quickly get attention from the right people.