-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add issue and PR templates and CODEOWNERS file #436
Conversation
060b3aa
to
974b67e
Compare
* Added CODEOWNERS file * Added links to CONTRIBUTION.md and COMMUNITY.md to README.md Signed-off-by: pietfried <[email protected]>
974b67e
to
fed9d52
Compare
Hi,
|
This is going to be really nice! Can it automatically set tags as well? Based on the issue type and maybe also the dropdown selection? I think the feature request can use some tweaking. It seems to be to focus mainly on the what and also on the how. I would suggest making required a "what is the problem/need" and "why is it a problem/need" since that really helps you to know what is requested. Those two could be in a single field as well. Then an optional field that leaves room for a suggestion on the how. That leaves room for the implementer to also look at the problem and find a good solution, potentially with the suggestion. |
Co-authored-by: Philip Molares <[email protected]> Signed-off-by: Piet Gömpel <[email protected]>
* added compile options in description for bug reproduction * Feature request: changed requirement of problem description to mandatory and solution to optional Signed-off-by: pietfried <[email protected]>
Signed-off-by: pietfried <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
Signed-off-by: Piet Gömpel <[email protected]>
No description provided.