Overview: Git and Looker
@mrosas wrote: 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...
View ArticleOverview: Git and Looker
@Y_Duan wrote: Is it possible to point production to a different branch, like release branch, than master? Read full topic
View ArticleOverview: Git and Looker
@ryan.dunlavy wrote: 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...
View ArticleOverview: Git and Looker
@FAR wrote: Hi @ryan.dunlavy, Has there been any update on this? Read full topic
View ArticleOverview: Git and Looker
@jay.hester wrote: 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...
View ArticleOverview: Git and Looker
@alexis_charrier wrote: 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...
View ArticleOverview: Git and Looker
@izzy wrote: alexis_charrier: Any news about the ability to point production to a different branch than master ? That feature request is being tracked here: Set Production branch to something other...
View ArticleOverview: Git and Looker
@cj.gunn wrote: 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...
View ArticleOverview: Git and Looker
@izzy wrote: cj.gunn: 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...
View ArticleOverview: Git and Looker
@izzy wrote: Just gave it a little test, and everything seemed to work okay— But my gut is still telling me that if you end up hitting the deploy webhook or something, things might break. Anyone have...
View ArticleOverview: Git and Looker
@cj.gunn wrote: Izzy, I agree it’s probably best practice to just start with an empty repo. No need to introduce unnecessary complexity. I’ll keep my non-core Looker code in a separate repo. Thanks!...
View ArticleOverview: Git and Looker
@Maria_Jabon wrote: Is there away to programmatically push changes to production? Read full topic
View ArticleOverview: Git and Looker
@izzy wrote: I don’t believe we have any API endpoints that actually manage git flows— But all of that could be handled programmatically via github APIs (or, just git on the command line, which I...
View Article