git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Checkout branch and prune everything related to previous checkout (incl. LFS remains)

From
Mateusz Loskot <mateusz@loskot.net>
Date
Jan 27, 2019, 00:16 UTC
Message-ID
<CABUeae_tm__uvHH74UARG805uTa2Sf0v6wYk=pmKvxxH3kvQ8A@mail.gmail.com>
Hi,

I have a repo of a superproject with number of submodules. lots of files of both are in Git LFS. The repo comes with multiple long-lived release branches. The complete clone transfers 20 GB of Git and Git LFS objects. Checkout of master deflates the total repo to 40 GB in total, that is the objects and the working tree files together.

Let's consider three separate clones as canonical way to create three working copies, one per the long-lived branch:

``` git clone --branch master --recursive --jobs 8 https://repo repo_master git clone --branch release/1.0 --recursive --jobs 8 https://repo repo_release1 git clone --branch release/2.0 --recursive --jobs 8 https://repo repo_release2

```
I'm trying to work out a network-optimised equivalent of the above:
- clone once with the default master checked out
- make multiple copies of the cloned repo
- checkout release branches

How to checkout an existing branch fetched from remote, delete the previous branch and clean up any remains?

How to clean up everything related to the previously checked out master and its working tree, any cached previous LFS downloads etc.?

But, to keep the history of origin/master.
Here is what I have come up with for the the network-optimised workflow:

``` git clone --branch master --recursive --jobs 8 https://repo repo_master

cp -a repo_master repo_release1 cp -a repo_master repo_release2

cd repo_release1 git checkout -b release/1.0 --track origin/release/1.0

git pull git submodule update --init --recursive --jobs 8

git branch -D master

git lfs prune git submodule foreach --recursive git lfs prune

git lfs checkout git submodule foreach --recursive git lfs checkout ```

Does it look correct or any steps are missing/redundant?
Does it make sense to run any of these, at which point?

git gc --aggressive --prune=now git submodule foreach --recursive git gc --aggressive --prune=now

Please, assume, no new commits will happen locally between the `git clone --branch master ...` and `cp -a repo_master ...`.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Message 1 of 1 in “Checkout branch and prune everything related to previous checkout (incl. LFS remains)”
  1. Mateusz LoskotJan 27, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.