There's nothing more frustrating than getting an incomplete bug report. I've often seen bug reports containing a useless "{x} feature doesn't work"; no steps to reproduce, no URL, no browser or device information, just a hopelessly vague message. Similar is receiving a pull request or patch which doesn't state its intent and doesn't provide steps to test (and what about unit tests?). Now that many projects are public, most on GitHub, I've seen a massive rise in these types of sparsely documented issues and pull requests.
没有比不完整的错误报告更令人沮丧的了。 我经常看到错误报告包含无效的“ {x}功能不起作用”; 没有重现步骤,没有URL,没有浏览器或设备信息,只是一条毫无希望的模糊信息。 类似的是接收到一个拉取请求或补丁,该请求未声明其意图且未提供测试步骤(单元测试又如何?)。 现在,许多项目都是公开的,大部分在GitHub上,我已经看到这类稀疏记录的问题和请求请求的数量大大增加。
I recently found out you an create pull request and issues templates so that when the user goes to file a pull request or issue,