Git hook 可以发送关于回购更改的电子邮件通知

Another, more modern way to do this is with git-multimail, as suggested by Chords below.

This is how you did it in 2009.

You could add something like this to your post-receive hook in $GITDIR/hooks, or use the script in the contrib directory of the source (Available here)

I managed to do this, but had to opt for using the contrib script, not the other (perl) script by Alexandre Julliard. It seems fancier and more configurable, but with postfix I had no mail command which would accept "-s"? Here's my way:

http://pastie.textmate.org/695323

It would be nice to show some more info, like the full patch, gitweb link and commit graph as well, but this script can only do the first - if I play around with hooks.showrev it seems.

Anyway, cheers and thanks for the suggestions!

setting hooks.showrev is making no distinguishable difference? :-/

Sample conf:

# less users/cj.git/config
[core]
repositoryformatversion = 0
filemode = true
bare = true
[hooks]
mailinglist = cj@yoga.ee
showrev = "git show -C %s; echo"
emailprefix = "[sabu gitosis server] "

This is my way of send email notification to users every time some one push to the repository.

Setting Up Git Commit Email Notification

It's based on Andy Parkins's scripts. I change it to used SMTP to send email. Of course, gmail's SMTP can also be used.

Robin Sommer's git-notifier generates also very nice summaries in the following format:

Subject: [git/git-notifier] master: Adding www target to Makefile. (7dc1f95)


Repository : ssh://<removed>/git-notifier


On branch  : master


>---------------------------------------------------------------


commit 7dc1f95c97275618d5bde1aaf6760cd7ff6a6ef7
Author: Robin Sommer <robin@icir.org>
Date:   Sun Dec 19 20:21:38 2010 -0800


Adding www target to Makefile.


>---------------------------------------------------------------


Makefile |    6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)


diff --git a/Makefile b/Makefile
index e184c66..9c9951b 100644
--- a/Makefile
+++ b/Makefile
@@ -5,6 +5,8 @@ VERSION   = 0.1


DISTFILES = git-notifier README COPYING


+WWW = $(HOME)/www/git-notifier
+
all:


dist:
@@ -13,3 +15,7 @@ dist:
cp $(DISTFILES) git-notifier-$(VERSION)
tar czvf git-notifier-$(VERSION).tgz git-notifier-$(VERSION)
rm -rf git-notifier-$(VERSION)
+
+www: dist
+   rst2html.py README >$(WWW)/index.html
+   cp git-notifier-$(VERSION).tgz $(WWW)

If you use windows, scm-notifier would be helpful.

Not exactly a full answer since it is Github-specific, but if you happen to use Github it is extremely easy to configure "Service Hooks".
For each repository you wish to monitor, enter Settings / Service Hooks.
There are plenty of available integrations, such as Trac, Twitter, Amazon SNS, Jira, Asana, Bugzilla, FogBugz, IRC, Jabber, Pivotal Tracker, Trello and Email....
Simply select email and feed it with a group email address.
We use the email notifications to sync our developers.

Here is the simplest solution I've found:

1) Log in to your gitHub account on github.com

2) In the main tab click on Settings

3) From the main navigation choose Service Hooks

4) From Available Hooks choose Email

5) Fill in your email address in field Address

6) Check the checkbox Send from Author

7) Check the checkbox Active

8) Click on Update Settings

Optional: You can click on Test Hook for testing, check your inbox you should receive email.

Also there are images made according to the process:

And now for the grand final I have the answer which is tested and approved at my side.

How to send email to ALL development team members, when gitHub's Service Hooks->Email allows only at most 2 recipients }.

The answer is combination of Service Hook->Email @ GitHub && Google groups

1. First login to your google account
2. Go to Google Groups and at the top click on Create Group
3. Type in Group Name, Group email address (will copy/paste into GitHub Service Hook->Email Address), Group description
4. After that hit Create button at the top, your new group should be created now
5. After that in the menu to the left hit Invite members and type in the email addresses of your team mates
6. After that hit Send invites (when your members accept invitation) they are now formally members of this group
7. In the menu on the left click on All Members and check the 4th column called Delivery, every team member should have option All Email.
8. After that I would like to credit Mr. Clement Escoffier and please do follow his guidelines @ Clement Escoffier::Send Github commits to a Google Group on how to finish it. {Thank you Clement :)}
9. If the link becomes unavailable here is another link to my gDocs @ PDF version of Clements guide

If you use GitLab you can use the 'Email-on-push' project service for this, it can be found under services in project settings.

You can use pre-commit:

#!/usr/bin/env ruby


require 'mail'


Mail.defaults do
delivery_method :smtp,
address: 'smtp.gmail.com',
port: 587,
user_name: '...',
password: '...',
authentication: 'plain',
enable_starttls_auto: true
end


changes=`git diff --cached --unified=0 Gemfile Bowerfile`


unless changes.empty?
Mail.deliver do
from     '...'
to       '...'
subject  '[PROJECT] Plese confirm team can use libraries'
body     changes
end
end

Install:

cd project
cp pre-commit .git/hooks
chmod +x .git/hooks/pre-commit
gem install mail

Test:

echo "# some change" >> Gemfile && git commit -m 'some change' Gemfile

In GitLab under your repository:

1. Click on Setting.
2. When setting expands there you will see Integrations. Click on it.

There opens a new page Emails on push

3. Locate and select Send from committer.
4. Also, enter the Recipients with comma separated located at the last field.

Also there is an option for Disable code diffs which exclude possibly sensitive code diffs in notification body. It is optional.

For more details: Click Here