Open vlad-stoian opened 5 years ago
Some of the lock repos can get super big really fast, especially if multiple teams/pipelines are using the same repo.
An idea is to use shallow clones, since we don't necessarily need the full history of the repo, we just need the latest state.
More about it here: https://www.perforce.com/blog/git-beyond-basics-using-shallow-clones
What do y'all think?
Some of the lock repos can get super big really fast, especially if multiple teams/pipelines are using the same repo.
An idea is to use shallow clones, since we don't necessarily need the full history of the repo, we just need the latest state.
More about it here: https://www.perforce.com/blog/git-beyond-basics-using-shallow-clones
What do y'all think?