This seems like less of an integration and more of a way to share updating .png images of your saves/revisions, no? The title got me excited that there was a serious integration going on :)
We actually use to have several "more serious" over-engineered integrations with a few services, as you can read in this now-ancient blog post: http://layervault.tumblr.com/post/37190358364/introducing-outposts
As it turns out, not many people used them, because they failed a simple test: was this easier than moving a file into place? Was this easier than just using both services as intended? Does this provide any value? At one point, we had built a file picker within LayerVault, that allowed you to choose where in Basecamp, GitHub, or Dropbox you wanted the file to go. It was much more difficult to use than just pasting an image in any of those services.
Since then, the integrations that we've worked on are automatic, lightweight, flexible, and universal. Most of the value it provides is in the automation, i.e. you don't have to continuously update designs as they change.
Thanks for the feedback and be on the lookout for more things from us.
Thanks for the reply. Its actually a neat feature of LV to have dynamic .png files that you can share with devs. I'm not even sure what a real github integration would look like at this point, but I look forward to what you guys come up with.
Maybe you could create an issue on Github directly from LayerVault?
So instead of popping up to github.com, you could do everything on LayerVault's website (using the Github API). That's more like an integration on my POV.
Hey Kelly, how are you guys handling invalidating githubs caching of image assets behind their proxy?