Skip to content

Use shallow git clones #40

@vlad-stoian

Description

@vlad-stoian

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions