chore: improve issue and PR templates#404
Conversation
|
@slnode test please |
|
Do we need |
dhmlau
left a comment
There was a problem hiding this comment.
Do we want the security vulnerability template too? https://github.com/strongloop/loopback/pull/4266/files#diff-f66a7d4cdb1e7589643b3ee760ce09b6
jannyHou
left a comment
There was a problem hiding this comment.
+1 for disabling the vulnerability issue reporting. https://github.com/strongloop/loopback/pull/4266/files#diff-f66a7d4cdb1e7589643b3ee760ce09b6
Otherwise LGTM 👍
|
@agnes512 @dhmlau I made it consistent with loopbackio/loopback-next#4030, so that they're redirected towards email instead. I think we should keep it disabled like @jannyHou (and change loopback and loopback-connector to be consistent), but do you think we should allow security vulnerability issue reporting? |
Description
Improve issue and pull request templates to match
loopback-next.Related issues
Checklist