[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-07-30(UTC)"],[],[],null,["# Migrating to a new Git repository\n\nIf you have a LookML project that is connected to a Git repository, you might want to move that project's LookML to a new repository.\n\n\nThere are two possible approaches to this problem, both of which are described in the following sections:\n\n- [**Reset the Git connection**](#simple_solution): This simple solution preserves all personal and shared branches in Looker and is suitable for the majority of use cases.\n- [**Clone the Git repository**](#advanced_solution): This advanced solution is preferred when it is important to be able to immediately see the complete history of all branches ever used through your Git provider's UI.\n\nSimple solution: Resetting the Git connection\n---------------------------------------------\n\n\nIf you [reset the Git connection](/looker/docs/setting-up-git-connection#integrating_looker_with_git) and enter a new Git repository URL, then the LookML will be moved over to that repository. All saved changes in personal and shared branches will be maintained and usable in Looker. At first, your Git provider's UI will only show the master branch and its history. Other branches and their history will appear the next time a commit is made to that branch. To migrate to a new repository using this method, follow these steps:\n\n1. Navigate to the [**Project Settings** page](/looker/docs/git-options#project_settings) for that project.\n2. On the [**Configuration** tab](/looker/docs/git-options#configuration) of the **Project Settings** page, select the **Reset Git Connection** button.\n3. On the **Configure Git** page, enter the new Git URL (the Git URL for the repository to which you want to migrate), and then select **Continue**.\n4. If you are using SSH to connect, be sure to select **Reset Key**. Otherwise, the same SSH key will be used, which can cause a conflict if both repositories are hosted by the same service (in this case, GitHub).\n5. For SSH connections, add the new deploy key to your Git repo, and be sure to grant write access in the Git repo deploy key settings. If you are using HTTPS, enter the login credentials for your Git repo. See the [Setting up and testing a Git connection](/looker/docs/setting-up-git-connection#integrating_looker_with_git) documentation page for full instructions on setting up Git.\n\n\nOnce you have followed these steps, your project will be connected to the new repository.\n\u003e **Note:** Your project LookML will not appear in the master branch of the new repository until you [deploy your project to production](/looker/docs/version-control-and-deploying-changes#deploying_to_production). Unless you deploy to production, your LookML code will appear only on your development branch in the new repository after [you commit the code](/looker/docs/version-control-and-deploying-changes#committing_changes), or push it to remote (a [Git command](/looker/docs/git-command-reference#push_changes_remote) available in the [**Git Actions** panel](/looker/docs/git-command-reference)).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nAdvanced solution: Cloning the repository\n-----------------------------------------\n\n\nThe [simple solution described previously](#simple_solution) will preserve the history of all branches, but only the master branch and its history will be visible in the GitHub UI at first. Once a commit is made on a personal or shared branch in Looker, that branch and its history will appear in the GitHub UI. A more advanced solution is necessary to immediately view all branches and their history through the GitHub UI.\n\n\nFirst, you need to have access to the original repository in GitHub (or other Git provider). You can find the repository URL at the bottom of the project settings or project configuration page.\n\n\nFor this example, suppose that `git@github.com:looker/PROJECT_NAME.git` is the original repo and `git@github.com:your_organization/PROJECT_NAME.git` is the new repo:\n\n1. Clone the original repository onto your computer, and pull down the branches you want to preserve.\n\n ```\n git clone git@github.com:looker/PROJECT_NAME.git\n cd PROJECT_NAME\n git checkout master\n git pull\n ```\n2. Reset the repo's remote URL. See the [GitHub documentation](https://help.github.com/articles/changing-a-remote-s-url/) for more information.\n\n ```\n git remote -v\n ```\n\n This shows you the remote(s) to which your repo is currently pointing. The results will look something like this: \n\n ```\n origin git@github.com:looker/PROJECT_NAME.git (fetch)\n origin git@github.com:looker/PROJECT_NAME.git (push)\n ```\n3. Next, set the origin remote to the new repo:\n\n ```\n git remote set-url origin git@github.com:your_organization/PROJECT_NAME.git\n git push origin master\n ```\n4. Now, to bring in history and files for dev branches, you'll need to do `git checkout dev_branch_name` and `git push origin` for each dev branch. This can be done manually or in a loop in a script such as shown in the following example:\n\n ```\n #!/bin/bash\n for branch in $(git branch --all | grep '^\\s*remotes' | egrep --invert-match '(:?HEAD|master)$'); do\n git branch --track \"${branch##*/}\" \"$branch\"\n done\n ```\n\n Then push the branches with `git push --all`.\n5. Reset the Git connection in Looker to this new URL and set up a deploy key on this new repo (see the [steps in the simple solution section](#simple_solution) earlier on this page)."]]
