We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
精读《When You “Git” in Trouble: a Version Control Story》
本期我们看一篇比较轻松的文章,与 git 相关,大家可以讲讲自己与 git 的故事,如何通过 git 解决各式各样的冲突,以及多年使用 git 老司机们的心得和感悟。 精读不仅仅只关注于文章本身,文章只是个引子,更希望大家积极参与互动与讨论,才是精读的精髓之处。
本期精读文章地址:https://hackernoon.com/when-you-git-in-trouble-a-version-control-story-97e6421b5c0e
参与讨论地址:#49
The text was updated successfully, but these errors were encountered:
看到我司有三种 git 开发方式,分别是主干部署、分支部署和 gitflow,个人项目的话主干部署真的很方便,非常适合快速迭代。不过对外项目基本都不敢用主干部署,风险太高。
Sorry, something went wrong.
项目基本都按人负责,而且基本都是一个人对多个项目,master部署不要太爽歪歪.... 现在后端应用都是强制分支开发,部署的时候自动合并,前端就没固定到流程中,感觉以后也可以放到工程体系中优化哦~
No branches or pull requests
精读《When You “Git” in Trouble: a Version Control Story》
本期我们看一篇比较轻松的文章,与 git 相关,大家可以讲讲自己与 git 的故事,如何通过 git 解决各式各样的冲突,以及多年使用 git 老司机们的心得和感悟。
精读不仅仅只关注于文章本身,文章只是个引子,更希望大家积极参与互动与讨论,才是精读的精髓之处。
本期精读文章地址:https://hackernoon.com/when-you-git-in-trouble-a-version-control-story-97e6421b5c0e
参与讨论地址:#49
The text was updated successfully, but these errors were encountered: