{"issue":{"milestone":null,"title":"Email notifications for collaborator commits","created_at":"2012-01-01T12:54:21Z","user":{"id":1105372,"login":"ophian","url":"https://api.github.com/users/ophian","gravatar_id":"2f4b420fbc41d1ca3f78186b267dac9a","avatar_url":"https://secure.gravatar.com/avatar/2f4b420fbc41d1ca3f78186b267dac9a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"updated_at":"2012-01-01T13:13:44Z","state":"open","labels":[],"id":2697106,"html_url":"https://github.com/s9y/Serendipity/issues/1","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"*Happy new Year to all of you*\r\n\r\nYou might have noticed that something is missing in the current briefing of organization members. There are no email-notifications for commits and keeping track of real changes is difficult, especially for larger organizations or being a member of some, as you have to check in to the website permanentely. (There are commit hooks, and one of them is email, but only one email address can be provided, users can't choose to listen or not, like all the other notifications.) Commits show up only in the news feed or by adding a comment to each pushed commit. First is bad as you have email and/or news feed to look up for; the Second expects some extra work by any pushing collaborator.\r\n\r\nThere have been others wishing this feature, like:\r\nhttp://stackoverflow.com/questions/552360/git-push-email-notification\r\nwhich leads to some scripts enabling commit notifications. (there are more out there)\r\n\r\nAs I am still far away to understand all the official or hidden gems of gitting, I started to know about Git having a way to fire off custom scripts when certain important actions occur. There are two groups of these hooks: client side and server side. The client-side hooks are for client operations such as committing and merging. The server-side hooks are for Git server operations such as receiving pushed commits. \r\n\r\nIn our case we need to use something like the server-side POST-recieve Hook to execute a commit mailing list script, right? \r\nThis has to be filled with all push/pull collaborator email adresses, unless someone does not want it and off we go.\r\nThe script can be be customized to show more or less detailed commit statements.\r\n\r\nIs that possible, Garvin?  Is it worth to add it to s9y/repo org? And are all other Collaborators willing to have that?\r\n\r\nIan\r\n*(and here my knowledge currently stops, so don't ask me to do this ... )*","number":1,"url":"https://api.github.com/repos/s9y/Serendipity/issues/1","comments":3,"assignee":null},"comment":{"created_at":"2012-01-01T13:13:44Z","user":{"id":1105372,"login":"ophian","url":"https://api.github.com/users/ophian","gravatar_id":"2f4b420fbc41d1ca3f78186b267dac9a","avatar_url":"https://secure.gravatar.com/avatar/2f4b420fbc41d1ca3f78186b267dac9a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"updated_at":"2012-01-01T13:13:44Z","id":3324465,"body":"Am 01.01.2012 13:59, schrieb Matthias Mees:\n> Maybe I'm thinking too simple here, but how about subscribing to https://github.com/s9y/Serendipity/commits/master.atom …? Why does it have to be email? (Myself, I'm kind of annoyed by all the email notifications of discussions.)\n>\n\nNo, not simple. That is what I said. You can either have that by feed \n(including commits, but missing some others) or/and by email (finetuned \nfor yourself in the notification label of your Account) missing the commits.\n\nMy talking was about adding commit notification to the email \nnotifications structure.\n\n@Joseph\nhaving a (additional) mailing list a la google groups is another option, \nbut it does not really help here, others than opening even more work to \nfollow and push ...","url":"https://api.github.com/repos/s9y/Serendipity/issues/comments/3324465"},"action":"created"}