Add global issue templates #53
Conversation
We also have PR templates at least in ORM, but I do not think they are used at all, since you have to add a `?template=the_template.md` parameter to enable them.
|
|
||
| We try to keep Github issues for bug reports and feature requests only. If | ||
| you have a question, please ask it on Stack Overflow or in one of the channels | ||
| mentioned at https://www.doctrine-project.org/community/index.html |
There was a problem hiding this comment.
ORM can keep its own template for this, that hints at github discussions instead.
There was a problem hiding this comment.
ORM, for example, has Support Questions in GitHub Discussions. I don't know if those should be also enabled in other repositories, but it looks like those won't be configured with a markdown template afaik.
greg0ire
requested review from
beberlei,
morozov,
alcaeus,
ostrolucky,
SenseException,
derrabus,
malarzm and
stof
|
|
||
| <!-- | ||
| Provide a failing Unit or Functional Test - you can submit one in a Pull | ||
| Request separately, referencing this bug report. | ||
| If that is too difficult, provide a link to a minimal repository containing an | ||
| application that reproduces the bug. | ||
| If the bug is simple, you may provide a code snippet instead, or even a list of | ||
| steps. | ||
| --> |
There was a problem hiding this comment.
A full pull request with a fix would be welcome too. Some people still might not know that they can already provide a fix for a bug that they found in Doctrine code and just need a nudge into that direction.
There was a problem hiding this comment.
Is this rather for non-technical description of a new feature? Otherwise I would also suggest something like an expected behaviour on how the creator of the feature request believes how this feature could be implemented.
We also have PR templates at least in ORM, but I do not think they are used at all, since you have to add a
?template=the_template.mdparameter to enable them.