The content of this article has been updated and migrated to a Looker Help Center article
If your workflow relies on editing LookML outside of Looker, then you’ll want to hit this endpoint every time you make a commit in your repository.
For a Github repo, you can set this up to happen automatically.
Once in the repo, navigate to Settings -> Webhooks -> “Add Webhook”
Enter the endpoint and choose which events should trigger the webhook (commit, release, etc).
Is there a way to rollback Looker to an older commit/tag id or does it always pick the latest master commit
Looker always picks the latest master commit. You can, however, roll back to the commit in git outside of Looker (like in github or your source control provider of choice), and then hit the deploy webhook as described in this post (we also have a help center article here: https://help.looker.com/hc/en-us/articles/360001288268-Deploy-Webhook-Pulling-From-Remote-Git-Repository) to sync Looker up to that.
So you totally can do it, just not directly from within the product.