-
Notifications
You must be signed in to change notification settings - Fork 270
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
Issue template format looks incorrect #37
Comments
Ah yes, now I understand how this works (had not used the issue templates before). Should we have few different templates perhaps? For example the one that is there already is "report a bug" and then "general discussion" and so on. |
No worries I've never used them either! 👍 I was thinking exactly that. For instance, one template could be for a bug fix (where we ensure people have the proper version installed, model works outside Talos, etc...). Another could be for a suggestion of a feature (where those checks might not be required). One more for documentation. Etc... |
Something went wrong this (updated directly to master after making changes to the template). I think it has to do with the way Github.com manages the templates directly from UI (can't use both the Github.com UI way and editing the file way and then committing change). I think it might be best to handle finalizing contribution guidelines and this together (I also need to create FAQ based on the experiences so far...which would be useful for the "question to ask" issue template. |
Sounds good. Let me know if you need any help! |
You're most welcome to help, thanks! :) Maybe I can take care of the FAQ one, but I will wait once you have the others up and follow the same procedure as you've used in order to avoid the same I had caused now. |
This was fixed, so closing. Thanks! |
For instance, trying to raise an issue...
I would wager that "How to raise an issue" is not a valid issue format! @mikkokotila I can look into this if you'd like. Let me know what you think.
Note that I've opened this issue by clicking "Open a regular issue"!
The text was updated successfully, but these errors were encountered: