openage
openage copied to clipboard
SFTtech
Adding PR/ISSUE Templates for this repo
Greetings! I would like to add some PR and ISSUE templates for this repo if possible.
You can tell me what to categorize like Bug Reports, New Feature... like that.
In PR there would be the Issue Number(if applicable), Description, Screenshots(if any) and other stuff like checkboxes that state the contributor has read contributing guidelines.
If possible kindly assign me this issue under hacktoberfest! Thanks!
Sure, this wouldn't hurt :)
~~Can you try using the new issue forms for this? The old template format is probably also fine.~~ (disregard that, see below)
We didn't use issue templates so far since we had the time to answer to each request individually, so people don't need to be restricted by some random input form. If we find that some form is useful with github's current implementation restrictions, we should always allow free form input - I personally don't like filling forms which request infos i'm very certain not useful for the request.
As long as we can easily request followup infos in an interactive way, I would rather not use issue form fields 🥲
@TheJJ Yeah maybe you're right on this. I wouldn't mind issue/PR templates though, especially since sometimes new contributors seem to not have a clue what to do/write, e.g. they forget to add their name to the copying file...
Yea, so if we can do it in a optional way that's attractive for inexperienced users, I think we could benefit.
Sure, this wouldn't hurt :)
~~Can you try using the new issue forms for this? The old template format is probably also fine.~~ (disregard that, see below)
hmmm ok will see what i can do!
Yea, so if we can do it in a optional way that's attractive for inexperienced users, I think we could benefit.
ye sure there be can the normal blank template alongwith it
We didn't use issue templates so far since we had the time to answer to each request individually, so people don't need to be restricted by some random input form. If we find that some form is useful with github's current implementation restrictions, we should always allow free form input - I personally don't like filling forms which request infos i'm very certain not useful for the request.
As long as we can easily request followup infos in an interactive way, I would rather not use issue form fields 🥲
Issue forms or templates don't limit this experience at all, they give a guideline rather. As you can see on the screenshot, you can still choose a blank issue without any constrains. So it's an addition and not a limitation to the current process. It just guides someone new through the process of reporting/articulating their problem enough, to make themselves understood to the devs of the software.
