Overview: Git and Looker

open
low_priority
reply
(Margaret Rosas) #1

For information on using Git with Looker, see this page in our documentation.

Looker integrates with Git services (e.g. GitHub, GitLab, Bitbucket, Phabricator Diffusion) for LookML source code management. Each LookML project corresponds with a Git repository. Looker uses Git to record changes and manage file versions.

Starting in 3.20, we have changed the workflow behind the scenes for LookML code deployments to include developer branches as described below:

  • Each user’s developer mode now correlates to a branch
  • Commit Changes will sync changes with Git service
  • Deploy to Production will update production environment by merging that branch to master

4 Likes

What does Deploy to Production mean? (3.20+)
(Y Duan) #2

Is it possible to point production to a different branch, like release branch, than master?

1 Like

(Ryan Dunlavy) #3

Hey @Y_Duan,

It is not currently possible to point production to a branch other than master, but this is an option that the product team is looking into adding. I will let them know you are looking forward to having that option!

0 Likes

#4

Hi @ryan.dunlavy,

Has there been any update on this?

0 Likes

(Jonathan Hester) #5

Hi Far,

There is no definitive timeline set on this request as of yet but I can see Friartuck’s interest in this feature has been mentioned in the request to the product guys. We will let you know if the status changes!

Thanks,
Jay

0 Likes

(Alexis CHARRIER) #6

Hello guys,

Any news about the ability to point production to a different branch than master ?
It would be great to unlink production version from master and merge master to production only when needed.

Thanks,

Cheers

0 Likes

(Izzy) #7

That feature request is being tracked here: Set Production branch to something other than master.
@yuriy has also posted a clever workaround in that thread, check it out.

0 Likes

(C.J.) #8

I am in the process of moving our repo from Looker’s Git repo to our own company’s hosted Bitbucket instance. Is it best practice to start with an empty repo or can I use an existing one? Does having other files in the repo cause an issue for Looker? For instance, can I have my own DB scripts that create the Looker and Looker PDT users/permissions in the same repo that Looker uses for its LookML?

0 Likes