Github和Kiln之间的自动同步 [英] Automated sync between Github and Kiln

问题描述

我是一名前端设计师，并没有很大的编程背景。我做CSS / html和一些JavaScript。我们公司的技术团队已将我们的版本控制从Git（github）移至Mercurial（Kiln）。他们唯一的理由是获得Kiln的代码审查功能（我们使用Fogbugz并且喜欢它）。
$ b 问题在于前端和非开发人员在我们的版本控制一直在增加。我们使用hg-git在Heroku上进行部署，并用于git（从未与其他版本控制系统一起工作）。
我相信Mercurial是一个很好的工具，但我必须得出结论，我们在问题和错误上花费了太多时间。

我的想法是：有没有一种在github上使用git的方法，然后将所有提交等同步到Mercurial（Kiln）？然后，我们将使用git，并且仍然具有Kiln的代码审查功能。

希望您能提供帮助。我很想用解决方案回到我们的技术团队;）

解决方案

您设置的任何同步将会更多比刚学习Mercurial容易出错。 Git和Mercurial都是很好的工具，而且非常相似，所以如果不是逐个细分地完成任务，你会花一个小时的时间阅读关于你能够毫无问题地来回切换的差异。 p>

不太好的同步选项是：git-hg，hgit和Mercurial的转换扩展，以及Mercurial对git子库的支持，但是你会后悔其中的任何一个，我们需要对两个工具有更深入的了解，而不是单独使用它们两种。

要么让开发者切换回来，要么让他们重写你的部署给你的东西，但不要在同一家公司内跨越。

I am a frontend designer and don't have a large programming background. I do CSS/html and a bit of JavaScript. The tech team at our company has moved our version control from Git (github) to Mercurial (Kiln). The only reason for them is to get the code review feature of Kiln (we use Fogbugz and love it).

The problem is that the frontenders and non-developers working in our version control are funcking up all the time. We use hg-git to deploy on Heroku and are used to git (never worked with other version control systems). I am sure that Mercurial is a great tool, but I must conclude that we spend too much time on problems and errors.

My thought was: Is there a way to use git on github and then sync all the commits etc to Mercurial (Kiln)? Then we would get to use git and still have the code review features of Kiln.

Hope you can help. I would love to come back to our tech team with a solution ;)

解决方案

Any synchronization you set up is going to be more error prone than just learning Mercurial. Git and Mercurial are both great tools, and very similar, so if rather than going at it piecemeal task-by-task you spend a good hour reading about the differences you'll be able to switch back and forth without any problem.

Not-great options for synchronization are: git-hg, hgit, and Mercurial's convert extension, and Mercurial's support for git subrepositories, but you'll regret any of them because they'll require a greater understanding of both tools than using either of them alone would.

Either make the developers switch back or make them rewrite your deploy stuff for you, but don't bother straddling within the same company.

这篇关于Github和Kiln之间的自动同步的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！