-
Notifications
You must be signed in to change notification settings - Fork 182
chore: improve issue and PR templates #404
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
Conversation
|
@slnode test please |
|
Do we need |
dhmlau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+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? |
dhmlau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Improve issue and pull request templates to match
loopback-next.Related issues
Checklist