Web 开发人员和 Web 设计师的 Git 工作流程
我和我的合作伙伴正在构建一个 Web 应用程序,我正在寻找有关我们可以实施的 git 工作流程的建议。我是这个团队的开发人员,所以我希望将所有困难的版本控制(即合并和推送到生产)都在我的控制之下,但我希望我的合作伙伴 - 设计师 - 能够开始使用 git 并开始去学习它的一些优点。我不想要一个适合开发团队的工作流程,因为我想通过这个来帮助我的合作伙伴让他使用 git。我的想法是这样的:
设计师从我的本地计算机克隆 git:
designer:~/$git clone git://192.168.0.1/programmer/project.git
设计器分支并进行更改:
designer:~/$git co -b Designer-branch
Designer 将他的分支推送到我的机器:
designer:~/$git Push Designer-branch
我会将 Designer-branch 合并到主分支中:
程序员:~/$git co master 程序员:~/$git merge designer-branch
我将更改推送到我们的存储库:
programmer:~/$git push
我认为这最有意义,但我希望其他开发人员在使用时提供任何提示或技巧你尝试过让一名设计师加入 git 阵营。
谢谢!
My partner and I are building a web app and I'm looking for suggestions on a git workflow that we can implement. I'm the developer half of this team so I want to keep all of the difficult version control (i.e. merging and pushing to production) under my control but I want my partner - the designer - to be able to start to use git and start to learn some of it's goodness. I don't want a workflow that would be appropriate for a team of developers because I want to handhold my partner through this to get him going with git. What I'm thinking is something like this:
Designer clones git from my local machine:
designer:~/$git clone git://192.168.0.1/programmer/project.git
Designer branches and makes changes:
designer:~/$git co -b designer-branch
Designer pushes his branch to my machine:
designer:~/$git push designer-branch
I'll merge the designer-branch into the master:
programmer:~/$git co master
programmer:~/$git merge designer-branchI push the changes to our repo:
programmer:~/$git push
I think this makes the most sense but I'd love any tips or tricks that other developers have when you've tried to bring a designer into the git fold.
Thanks!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我唯一要补充的是使用功能分支并远离基于主干的开发。如果您正在解决冲突,请分享您如何使用 rerere 解决冲突:
http://progit.org /2010/03/08/rerere.html
rr-cache 目录内容可以通过符号链接共享到“helper”存储库。这样,其他人就可以将功能组合在一起,而不需要最初解决冲突的人的帮助。
谷歌“git flow”也是如此。它可以自动执行您在分支上执行的一些冗余操作。
希望这有帮助。
The only thing I would add is to use feature branches and stay away from trunk-based development. If you are resolving conflicts, share how you resolved them with rerere:
http://progit.org/2010/03/08/rerere.html
The rr-cache directory contents can be shared via symlinks to a "helper" repo. This way others can put features together and not require the assistance of the person who originally solved a conflict.
Google "git flow" as well. It automates some of the redundant things you do with branches.
Hope this helps.