We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: