每当有人提交更改时，如何将提交的更改的差异发送到整个项目？
我希望能够在提交时向所有参与项目的贡献者发送一条消息。这样，每个人都会看到贡献，并希望有人会看一下并发现错误等。此外，它为我们的老板提供了一种很好、简单（尽管有点难以理解）的方式来了解项目的进展情况。
我们现在正在使用 Mercurial。
I'd like to be able to send all the contributors working on a project a message whenever a commit is made. This way, everyone sees the contribution, and hopefully someone will take a look and spot bugs and whatnot. Furthermore, it provides our bosses with a nice and simple, if a little incomprehensible, way to get an idea of how the project is progressing.
We're using Mercurial right now.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否尝试过 notify 扩展程序？此提交挂钩可以发送电子邮件通知。
Have you tried the notify extension? This commit hook can send out email notifications.
最简单的方法是将其合并到您的 CI 流程中（如果您有的话）（即在您的构建中添加一个任务来向组发送垃圾邮件）。
也就是说，我强烈建议您不要做这样的事情。
首先，如果没有一些明确的流程来确定谁来审查什么，这就会变成噪音，并且很可能会被忽视。
其次，电子邮件并不是审查代码的糟糕媒介。通过在编辑器中审阅代码，审阅者可以自由地使用 IDE 的全部功能来浏览代码。
第三，行动并不等于进步。向管理层表明事情正在发生并不意味着正在取得进展。
如果您希望管理层能够看到所取得的进展，请考虑使用任务板来反映待办事项、进行中的项目、已完成的项目等。
如果您想要更好的质量控制，请使用敏捷流程，例如 TDD 和配对以及自我管理。围绕能力和能力进行组织经验（也就是说，更好的开发人员正在指导较弱的开发人员）。
如果您想要有关何时引入错误的反馈，请使用持续集成。
The easiest way would be to incorporate this into your CI process if you had one (i.e. add a task to your build to spam the group).
That said, I would highly recommend you NOT do something like this.
First, without some defined process of who is to review what, this will just become noise and will likely get ignored.
Second, email makes for a poor medium to review code. By reviewing the code in an editor, the reviewer is free to use the full power of the IDE to navigate around the code.
Third, motion doesn't equal progress. Showing management that things are happening doesn't mean progress is being made.
If you want a way for management to see progress being made, consider using a task board that reflect backlog items, in progress items, items completed, etc.
If you want better quality control, use agile processes like TDD and pairing, and self-organize around ability & experience (which is to say that the better developers are mentoring the weaker developers).
If you want feedback about when bugs are introduced, use continuous integration.