Github级联合并的做法是什么? [英] What's the practice for Github cascading merge?

查看:66
本文介绍了Github级联合并的做法是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

github中是否有任何选项或实践可提供像bitbucket这样的自动PR级联(

Is there any option or practice in github which provides auto PR cascading like bitbucket (https://confluence.atlassian.com/bitbucketserver/automatic-branch-merging-776639993.html)?

基本上,如果我将PR合并到发布候选分支,它也会将更改也合并到master.

Basically if I merge a PR to a release-candidate branch, it will also merge the changes to master as well.

推荐答案

Github目前没有此功能,

Github doesn't have this capability at present and this feature is not mentioned in Collaborating with issues and pull requests help section. You can try to implement it with server-side hooks but it's not provided by Github as a repository configuration option.

也许这是因为Github建议 GitHub-flow ,它与Git-flow不同不要使用单独的候选发布分支.

Perhaps that's because Github suggests GitHub-flow which unlike Git-flow doesn't use a separate release candidate branch.

这篇关于Github级联合并的做法是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆