有没有标准的git工作流程？ [英] Is there a standard git workflow?

问题描述

此刻，我做错了，我从主人手中挣脱出来，当一切稳定时，我创建一个版本号并将其放入标记分支中。

根据我的理解，github上的大多数项目都有稳定的主人。 dev，这是所有改变的地方，标记版本和修补程序/补丁的额外分支，功能我觉得现在正在做，而不是正在进行的工作等等。

你把你的主人又称为稳定的，如果看起来确定的话，你通常会拉着你的主人。

我不认为我的理解是正确的。有一个'标准'git工作流程吗？有什么是'建议'吗？

解决方案

这个Git分支模型非常流行：

http://nvie.com/posts/a-successful-git-branching-model/

At the moment i am doing it wrong and i work off of master and when everything is stable i create a version number and put it in the tag branch.

From my understanding most projects on github have master which is 'stable'. dev which is where all changes are being made, tag for versioning and extra branches for hotfix/patches, features i feel like doing now instead of what is being worked on and etc.

You push your master aka stable and typically on pull request if it looks ok you would pull into your master

I dont think my understanding is correct. Is there a 'standard' git workflow? Is there anything thats 'suggested'?

解决方案

This Git branching model is rather popular:

http://nvie.com/posts/a-successful-git-branching-model/

这篇关于有没有标准的git工作流程？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！