为什么git提示我提交后合并提交消息? [英] Why is git prompting me for a post-pull merge commit message?

查看:132
本文介绍了为什么git提示我提交后合并提交消息?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近,在任何 git pull 之后,git已经开始产生我的文本编辑器,并要求提交合并提交消息。一条提交消息已经预先填好,我只需保存并关闭窗口即可完成提取。



过去,它会默默地进行合并,使用标准的提交信息(沿着 remote.com的合并分支'dev':/repo into dev 的行)。

我最近更新了git到版本1.7.11.3(通过homebrew),但想不到我可能做了什么改变这种行为。这是一个设置,还是有其他方式回到原来的方式?

解决方案

在git 1.7.10 ,git开发者决定合并提交可能太容易了。如此博客文章中所述,强制进行交互式提交消息行为应该使这些提交消息更加详细,并且可以减少不必要的合并的总体频率。



您可以使用 - no-edit 标志来避免这种行为,但是,不。合并提交,就像任何对历史的提交一样,应该很好地构建。你的历史应该是有用的。


Recently, following any git pull, git has started spawning my text editor, and asking for a merge commit message. A commit message is already pre-filled, and I just have to save and close the window to complete the pull.

In the past, it would do the merge silently, with a standard commit message (along the lines of Merge branch 'dev' of remote.com:/repo into dev).

I recently updated git to version 1.7.11.3 (via homebrew), but can't think of anything else I might have done to change this behavior. Is this a setting, or is there otherwise some way of getting back to the way it was?

解决方案

In git 1.7.10, the git developers decided merge commits could be made too easily. As explained in this blog post, forcing the interactive commit message behavior should make those commit messages more detailed and could reduce the overall frequency of unnecessary merges.

You can use the --no-edit flag to avoid this behavior, but, well, don't. Merge commits, like any commits to history, should be well constructed. Your history should be nothing but useful.

这篇关于为什么git提示我提交后合并提交消息?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆