GitHub贡献，拉取请求与新问题的礼节 [英] Etiquette of GitHub Contributing, Pull Requests vs New Issue

问题描述

如果您首先提交一个New Issue，然后讨论这个问题，问题？

或者你是否采取了一些主动性，代码，然后做一个请求并在那里讨论代码？

首先创建New Issue的关注点在于，如果您在执行请求之后，是＃创建的两个问题......看起来很浪费。

谢谢！

解决方案

不同之处很明显：如果您认为您无法贡献回补丁，请打开一个补丁新问题（遵循与此处描述的清单相同的清单） a>）。如果您认为可以通过一些补丁来解决问题，请分叉回购并制作 Pull Re任务（一旦您将补丁推回到您的分支）。

如果您先提出拉取问题，然后创建一个拉取请求，没有什么能阻止你引用拉取请求评论中的问题URL，以避免再次写入 你的修补程序的上下文。

I was wondering what the proper etiquette to contributing on GitHub is?

Should you submit a "New Issue" first and discuss the problem?

Or do you take some initiative, code, then do a "Pull Request" and discuss the code further there?

My concern with creating a "New Issue" first is that if you do a "Pull Request" after, there would be two issues #'s created... seems like a waste.

Thanks!

解决方案

The difference is quite clear:

• if you don't think you can contribute back a patch, open a "New Issue" (following the same kind of checklist than the one described here).
• if you think you can make some patch to fix the issue, fork the repo, and make a "Pull Request" (once you have pushed your patch back to your fork).

If you make a pull issue first, and then create a pull request, nothing stops you to reference the issue URL in your pull request comment, in order to avoid writing again the context of your patch.

这篇关于GitHub贡献，拉取请求与新问题的礼节的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！