This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
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!
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?...
