有关合作者向项目创建提交的新规则的讨论 #117
Replies: 12 comments 3 replies
-
|
已解决:仅在 dev 分支 commit,每次合并到主分支的时候pr和bump version |
Beta Was this translation helpful? Give feedback.
-
|
main分支仅在需要大版本更新时再提交PR |
Beta Was this translation helpful? Give feedback.
-
或许该作为一条不成文的规定? |
Beta Was this translation helpful? Give feedback.
-
啊?我已经提交了部分代码到main,我会在以后提交时直接提交到dev分支 |
Beta Was this translation helpful? Give feedback.
-
|
此议题仍需要进一步讨论。 我个人对
|
Beta Was this translation helpful? Give feedback.
-
|
总之我觉得这种处理办法还是抽象了点 |
Beta Was this translation helpful? Give feedback.
-
|
如果确实要使用这样的方法进行开发,那么由于 |
Beta Was this translation helpful? Give feedback.
-
|
如果不对大杂烩 这种情况下还不如直接提交来的好。 不是为了合并而合并。 |
Beta Was this translation helpful? Give feedback.
-
|
如果是因为希望减少 而且人为审查也很可能存在遗漏,我们或许还得添加测试用例,然后每次合并前跑一遍。 这里不得不说项目贡献者和项目协作者的区别,正是因为对方是项目协作者,所以才可以在无需项目主导者审核的情况下直接进行提交——我们人并不多,数出来也就三四个人,完全没必要限制的这么死,而且这么操作起来,我认为一点也不优雅。 |
Beta Was this translation helpful? Give feedback.
-
|
另外一个观点是,我觉得各位用 |
Beta Was this translation helpful? Give feedback.
-
|
综上所述,我不赞同强制实施 |
Beta Was this translation helpful? Give feedback.
-
|
还是有争议,因为我们还需要解决新的插件如要使用新的接口但用户可以获取到新接口插件的问题 |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
我注意到最近产生了很多拉取请求,但大多数拉取请求的改动都不大,但这些提交都以拉取请求的方式被合并到了主分支,这显然形成了对拉取请求这一工具的滥用行为。
很多的提交都可以直接提交到存储库的,又不是什么大的更改,完全没必要开
PR处理问题。我认为我们应该重视这件事?
Beta Was this translation helpful? Give feedback.
All reactions