Add issue template for better orientation#466
Conversation
|
@nhedger You're totally right, the only thing I'd have to do is to add the The downside is that EVERY project inside the ReactPHP organisation gets the same issue template. This may make sense for most projects (like dns, http, etc.) but not for something like reactphp/branding or reactphp/reactphp. I would instantly do this if GitHub had some kind of functionality to exclude specific repositories, but I didn't find anything similar. In conclusion: I am willing to take the slightly longer road and do it for every repository individually (which means only to copy-paste at some point 😄). Just feels right ^^ |
SimonFrings
force-pushed
the
issue_template
branch
from
fd78cc5 to
2d3064d
Compare
SimonFrings
force-pushed
the
issue_template
branch
from
2d3064d to
afe1c66
Compare
SimonFrings
force-pushed
the
issue_template
branch
from
afe1c66 to
86371dd
Compare
SimonFrings
force-pushed
the
issue_template
branch
from
86371dd to
ba05d1f
Compare
clue
left a comment
clue
left a comment
There was a problem hiding this comment.
@SimonFrings Thank you for the update, changes LGTM! 
4 participants
This pull request adds issue templates to this project.
With GitHub Discussions now activated on an organizational level (as discussed in #460), it makes sense to add issue templates to each ReactPHP repository to show users where they have to open up specific tickets:
issuesfor bug reports. These bugs will be fixed at some point and then belong inclosed issues. Additionally I won't add a bug template to reactphp/reactphp. IMO it makes no sense to report a bug in this repository. All bugs should be reported inside the related repo (http, socket, dns, etc.).I will file pull requests to add issue templates for each ReactPHP repository. Repos like https://github.com/reactphp/branding or https://github.com/reactphp/.github won't receive them (makes no sense).