there are, of course, quite a few ways to do this....
if you want active triggers, then I think the scripts have to be in the travis.yml of the repo with the source thats changing (i.e. axoloti_factory/community), what these triggers do though of course is 'open'.
they could simply 'ping another web server' , which in response could do a pull.
otherwise you could poll the repos... not as nice, but can work.
in the last post, what I envisaged was just having a compiled jar from @cpwitz in the factory/community repos (in a tools directory), so its just replaced when/if there is a new version (e.g. if the xml format changes)
there is another side to this for the future...
I would interested to know how users are using this, such that the new object browser could do something similar within the app.
... but it maybe that users are enjoying this because they can see if without starting the app, in which case, the object browser can help this :))