Skip to content

Feature Request Issue Template #39473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 14, 2022
Merged

Feature Request Issue Template #39473

merged 2 commits into from
Jan 14, 2022

Conversation

TanayParikh
Copy link
Contributor

@TanayParikh TanayParikh commented Jan 13, 2022

@TanayParikh TanayParikh requested review from mkArtakMSFT and a team as code owners January 13, 2022 01:06
@TanayParikh TanayParikh requested a review from a team January 13, 2022 01:06
@TanayParikh TanayParikh added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jan 13, 2022
@TanayParikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@TanayParikh
Copy link
Contributor Author

Retry not working due to #39477, need to do a full re-run.

@javiercn
Copy link
Member

@TanayParikh don't re-trigger the build for these types of changes as its wasteful.

Suggest you ask the build team to merge once you get sign-off instead.

@dougbu
Copy link
Contributor

dougbu commented Jan 14, 2022

@TanayParikh one downside of using forms in more issue templates is the inability to completely clear out the description. People who want to start from scratch need to go to https://github.com/dotnet/aspnetcore/issues/new or choose a template still using .md files. Is your plan to remove all .md templates, removing the second option❔ If yes, why❔

@TanayParikh
Copy link
Contributor Author

@TanayParikh one downside of using forms in more issue templates is the inability to completely clear out the description. People who want to start from scratch need to go to https://github.com/dotnet/aspnetcore/issues/new or choose a template still using .md files.

There's also a button at the bottom left of the issues page to create a blank issue:

image

That's what I normally use. If I'm running into an issue, I generally have a good idea of what details I may need to provide to either reproduce or debug the issue in the future. I suspect other repo contributors are also using the blank template via this or the methods you described. The template isn't too necessary for repo members/core contributors as we can always reach out and quickly get clarity if required. The template is primarily targeted for members of the community as it ensures the standard reporting process is followed (check for duplicate issues, issue details, repro steps, versions, etc.). Overall I really like the templates as I'm finding the quality of the issues (in terms of details provided and clarity) has improved after we switched to issue templates. This is likely an effect of them being easier to parse and complete, in comparison to editing a markdown textarea with a bunch of comments.

Is your plan to remove all .md templates, removing the second option❔ If yes, why❔

No, this was the last template I was planning on replacing as this (along with the main bug issue) are the most used templates.

Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the additional details @TanayParikh

@TanayParikh TanayParikh merged commit 2491b30 into main Jan 14, 2022
@TanayParikh TanayParikh deleted the TanayParikh-patch-1 branch January 14, 2022 19:59
@ghost ghost added this to the 7.0-preview1 milestone Jan 14, 2022
@TanayParikh
Copy link
Contributor Author

Merged & validated: #39534

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants