Skip to content

Conversation

@mainred
Copy link
Member

@mainred mainred commented Jun 10, 2020

What this PR does / why we need it:
I find people reporting issues in ths repo tend to not follow exactly the template, and I personal fell it's a bit complicated in its structure, so I simply the issue template to make it more report friendly.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Release note:

@matmerr
Copy link
Member

matmerr commented Jun 10, 2020

It looks like the gh issue templating has changed a little bit, perhaps we should adhere to those while we're making this change? Separate templates for CNI, CNS, and NPM issues?

https://help.github.com/en/github/building-a-strong-community/about-issue-and-pull-request-templates#issue-templates

@mainred
Copy link
Member Author

mainred commented Jun 11, 2020

It looks like the gh issue templating has changed a little bit, perhaps we should adhere to those while we're making this change? Separate templates for CNI, CNS, and NPM issues?

Excellent point, that was also my consideration to make less if-else explanation. But, considering issue and feature request for different components share the same items, for now, to be maintained

I am looking forward to split different components into different repos :)

@mainred
Copy link
Member Author

mainred commented Jun 17, 2020

@matmerr , thanks for your idea. I followed your idea and used issue builder to make one issue more clearly and focused.

@mainred mainred changed the title Simply issue template Simplify issue template Jun 18, 2020
@matmerr
Copy link
Member

matmerr commented Jun 26, 2020

I took these changes and refined it a little more in #592. Thanks @mainred!

@matmerr matmerr closed this Jun 26, 2020
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.

2 participants