-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Idea: add templates for Issues #4
Comments
It's great having you contribute to this projectFeel free to raise an Issue! Welcome to the community 🤓If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord chat and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know. |
Do you want to work on this @mstanciu552 or should we open a #first-timers discussion to invite more first-timers and getting them used to how issue templates work? |
We could open a discussion as I don't know if I will find the time with the wotk I need to do for school and my other projects.:yum: |
no stress @mstanciu552 , between all of us, we will get something done 🤓 |
There was a prior issue referring this in the EddieBot Repo(EddieBot#316: add issue templeates) Some brief relevant information from the discussion there:
|
Thanks for transferring the issue here @mstanciu552 👍 |
This idea comes from an Issue in the EddieBot repo, Issue #316.
We should add templates for Issues such as a template for idea, feature, fix, etc.
Additionaly, in the EddieBot repo there is a template for a bug type of issue.
@eddiejaoude mentioned in Issue #316 that we should add templates in this repo template for better scalability. We might want to move that here or make a bug issue template here as well.
I would like to handle this, but first I have to learn about GitHub Actions as I just got into Github and don't know too much about it.
Please share any thoughts on the matter.:yum:
The text was updated successfully, but these errors were encountered: