News for hackers. Stuff that matters.
Re:Gitwatch: Watch a Git repository for changes by zwischenzug on Saturday November 14, 2015 @04:16AM (#10565057)
I did this recently as a more generalised service for tracking changes to the output of commands:

https://github.com/ianmiell/alert-on-change/blob/master/READ...

It adds the concept of degree of change to the output triggering an alert.

Re:Gitwatch: Watch a Git repository for changes by oxplot on Saturday November 14, 2015 @07:59AM (#10565504)
This looks great. Have you thought about turning it into a unix filter?
Re:Gitwatch: Watch a Git repository for changes by zwischenzug on Saturday November 14, 2015 @08:10AM (#10565532)
Hmmm, good idea.
Re:Gitwatch: Watch a Git repository for changes by Too on Saturday November 14, 2015 @04:18AM (#10565061)
https://github.com/sickill/git-dude

This one is pretty similar and slightly more readable imo (if shell-scripts can ever be considered readable). Just replace the notify-function with whatever you want to execute instead.

Re:Gitwatch: Watch a Git repository for changes by sytse on Saturday November 14, 2015 @11:54AM (#10566280)
If you're using GitLab.com or GitLab EE it has a project service that sends you an email on every push with the diff of the commits.
Re:Gitwatch: Watch a Git repository for changes by nathancahill on Saturday November 14, 2015 @11:07AM (#10566072)
Different use case, but I can not recommend using Sibbell[0] enough. Especially when you have more than a handful of dependencies, tracking issues, fixes and their eventual release is crucial.

[0] https://sibbell.com/about/

Re:Gitwatch: Watch a Git repository for changes by fenollp on Saturday November 14, 2015 @04:00AM (#10565022)
Stupidly inefficient. `git ls-remote --heads --tags ‹URL›`
Re:Gitwatch: Watch a Git repository for changes by oxplot on Saturday November 14, 2015 @04:06AM (#10565035)
That only gives you the commit for the head of the branches. If there were multiple commits since you checked last, you'll miss some!
Re:Gitwatch: Watch a Git repository for changes by fenollp on Saturday November 14, 2015 @06:44AM (#10565348)
You will miss some. But then you just make a diff on the commits' SHA and only then you clone the repo (or fetch an archive, which is quicker).

You save a lot of time / bandwidth / space this way.

Re:Gitwatch: Watch a Git repository for changes by oxplot on Saturday November 14, 2015 @06:49AM (#10565357)
You only delay saving time and bandwidth — you eventually have to clone the repo for any ops other than checking the head SHAs and unless the repo is rarely updated, the delay will be short.
Re:Gitwatch: Watch a Git repository for changes by fenollp on Monday November 16, 2015 @11:25AM (#10575288)
Use git-archive or curl: gzipped source code is always smaller than a full versioned repo…
Re:Gitwatch: Watch a Git repository for changes by oxplot on Tuesday November 17, 2015 @05:32PM (#10584480)
You don't need the full versioned repo, just the top commit (ie cloning with depth=1). Also, git compresses the objects before sending them.