Skip to content

Conversation

@nabdelgadir
Copy link
Contributor

Description

Improve issue and pull request templates to match loopback-next.

Related issues

Checklist

  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide

@nabdelgadir
Copy link
Contributor Author

@slnode test please

@agnes512
Copy link
Contributor

Do we need .github/ISSUE_TEMPLATE/Security_vulnerability.md as what we did in loopback-connector? Or we only need it in that package?

Copy link
Member

@dhmlau dhmlau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@jannyHou jannyHou left a 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 👍

@nabdelgadir
Copy link
Contributor Author

@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?

Copy link
Member

@dhmlau dhmlau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nabdelgadir nabdelgadir merged commit ddb1c96 into master Nov 15, 2019
@delete-merged-branch delete-merged-branch bot deleted the chore/improve-issue-templates branch November 15, 2019 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants