Monorepo 中分布式团队的分支和发布流程
我们正在尝试将 3 个 Angular 应用程序(使用 NX 工作区)从它们自己的存储库移动到单个存储库/monorepo,因为它们可以共享公共库中的大量代码和资产,目前所有这些应用程序都由它们的独立团队处理,并且它们有他们自己的发布周期和冲刺。
但是将它们移至同一个存储库,我们无法决定如何设置分支和分支。发布策略使得每个应用程序都可以独立部署并且可以有自己的发布周期?
团队可以管理哪些功能可以转移到登台和生产?
We are trying to move 3 angular apps(using NX workspace) from their own repo to a single repository/monorepo because they can share lot of code and assets from common libs, currently all these apps are being handled by their independent teams and they have their own release cycle and sprints.
But moving them to same repo we are not able to decide how we can setup a branching & release strategy so that each app can be deployed independently can have their own release cycles?
And teams can manage what feature can be move to staging and production?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论