Open iteles opened 7 years ago
Even more so than with issues, I've noticed that PR descriptions are often very sparse.
My hypothesis is that this isn't due to laziness, it's due to a lack of 'inspiration' over what to actually write in the PR description.
Enter pull request (and issue) templates.
This should include:
Thanks for the tip @NataliaLKB !
We should also consider adding this to an .npmignore file as it's unnecessary for npm.
.npmignore
Great idea! if someone has time to prepare this PR we would be very grateful. 👍
@nelsonic @iteles Working on it!
Even more so than with issues, I've noticed that PR descriptions are often very sparse.
Enter pull request (and issue) templates.
This should include:
Thanks for the tip @NataliaLKB !
We should also consider adding this to an
.npmignore
file as it's unnecessary for npm.