You may occasionally find that the LookML you see in Looker’s production mode doesn't match the LookML on the master branch of your Git repository. This most commonly occurs for one of the following reasons:
- Pull Requests are enabled on the repository
- The LookML has been edited somewhere outside of Looker’s development environment, like:
- the Git repository itself
- another instance of Looker, like a staging instance
You can get Looker’s production branch in sync with the repository's master branch. Open a new tab and type in a URL following this format:
Replace [hostname] with your Looker URL, which is probably in a format like awesomecompany.looker.com or looker.awesomecompany.com. Replace [project name] with the name of the project you want to sync.
After you run this URL, a white screen with a success message will appear:
Now, your production mode in Looker has been updated to reflect your remote master branch. Your personal developer branch and shared branches are unaffected.
Many Git providers can hit webhooks like this one after every commit, or based on other events you define. This can help automate the process of keeping Looker in sync.
As of Looker 5.20, you can require a webhook deploy secret for pushing changes from your master branch to your production branch.