One scenario might be where you're committing the fix for a particular issue, but you know the issue you've resolved is a short term fix for the problem.
In this case it might be necessary to open another issue in light of the short term fix so that you know you need to provide a long term fix somewhere down the road.
Maybe in a situation where a bug-report includes several "sub-bugs" : the commit can solve one of those "sub-bugs", and create another report for the remaining "sub-bugs" ?
Or sometimes, if you commit some hacky patch to quickly solve an urgent bug, you might want to create another report to "correct the hacky patch", to create a long-term solution ?
发布评论
评论（2）
一种情况可能是您正在提交针对特定问题的修复，但您知道已解决的问题是该问题的短期修复。
在这种情况下，可能有必要根据短期修复打开另一个问题，以便您知道需要在未来的某个地方提供长期修复。
One scenario might be where you're committing the fix for a particular issue, but you know the issue you've resolved is a short term fix for the problem.
In this case it might be necessary to open another issue in light of the short term fix so that you know you need to provide a long term fix somewhere down the road.
也许在错误报告包含多个“子错误”的情况下：提交可以解决其中一个“子错误”，并为剩余的“子错误”创建另一个报告？
或者有时，如果您提交一些黑客补丁来快速解决紧急错误，您可能需要创建另一个报告来“纠正黑客补丁”，以创建长期解决方案？
Maybe in a situation where a bug-report includes several "sub-bugs" : the commit can solve one of those "sub-bugs", and create another report for the remaining "sub-bugs" ?
Or sometimes, if you commit some hacky patch to quickly solve an urgent bug, you might want to create another report to "correct the hacky patch", to create a long-term solution ?