3 ms·
Gitwatch: Watch a Git repository for changes
- fenollp 11y agoStupidly inefficient. `git ls-remote --heads --tags ‹URL›`
- oxplot 11y agoThat only gives you the commit for the head of the branches. If there were multiple commits since you checked last, you'll miss some!
- fenollp 11y agoYou 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.
- oxplot 11y agoYou 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.
- zwischenzug 11y agoI 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/README.md https://github.com/ianmiell/alert-on-change/blob/master/READ... It adds the concept of degree of change to the output triggering an alert.
- oxplot 11y agoThis looks great. Have you thought about turning it into a unix filter?
- zwischenzug 11y agoHmmm, good idea.
- Too 11y agohttps://github.com/sickill/git-dude 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.
- nathancahill 11y agoDifferent 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/ https://sibbell.com/about/
- sytse 11y agoIf 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.