当提交到版本控制需要开发人员更改他们自己的配置时 [英] When a commit to revision control requires a developer to change their own config

问题描述

当提交到修订控制中的更改需要开发人员获取更新的某些特定附加操作时，通知其他开发人员的最佳方法是什么，例如修改不在版本控制中的本地配置文件?

What's the best method to notify other developers when a change committed into revision control requires some specific additional action by the developer getting the update e.g. modify a local config file not in version control?

我目前正在提交消息中写入它，但似乎很容易错过.是否有任何版本控制系统提供了更好的方法来做到这一点?

I'm currently writing it in the commit message, but it seems like this could easily be missed. Do any revision control systems provide a better way of doing this?

其他人是如何做到这一点的，或者不应该有任何超出修订控制范围的必要更改?

How do other people do this, or should there never be any necessary changes that are outside of revision control?

我正在使用 mercurial，但那些使用其他形式的修订控制的人的回答也很有用.

I'm using mercurial but answers from those using other forms of revision control would be useful too.

推荐答案

应该很少有超出修订控制范围的必要更改.对于极少数情况，请使用开发人员拥有的常规通信渠道(如邮件列表或 IRC 渠道或类似的东西).无论如何，每个多开发者项目都需要这样的东西.

There should rarely be changes necessary that are outside of revision control. For the rare cases where they are, use the regular communication channel the developers have (like mailing list or IRC channel or something similar). Every multi-developer project needs such thing anyway.

这篇关于当提交到版本控制需要开发人员更改他们自己的配置时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！