<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=551408) </details> <!--IssueSummary end--> MR: Pending <!-- NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/devops/dev/create/remote-development/index.html#relationship-of-issues-to-mrs --> ## Description This is a followup to this discussion here: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/194906#note_2584517972 Currently we `unshallow` the entire cloned repo in a single `git fetch --unshallow` process. The unshallow is a 0-1 operation and the remaining git history becomes available only after the process completes. This can take some time for larger repos, i.e for the Gitlab monolith it takes ~30 minutes to do a full unshallow. We want to improve this process and unshallow repos iteratively so that users can have access to the immediate git history sooner. We can do this in several ways: ### Approach 1 * Git clone with depth of 1 * Unshallow upto depth 50 * Unshallow upto depth 500 * Unshallow remaining ### Approach 2 * Git clone with depth of 1 * Unshalllow upto 1 day prior * Unshalllow upto 1 week prior * Unshalllow upto 1 month prior * Unshallow remaining <!-- TODO: What kind of issue is this? Please uncomment and include one of the following: /label ~"type::feature" /label ~"type::bug" /label ~"type::maintenance" --> <!-- OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality. --> <!-- OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue! --> ## Acceptance criteria - [ ] Update shallow clone depth to 1 - [ ] Breakdown unshallow process into several stages - [ ] Logs added for each stage ## References - https://gitlab.com/gitlab-org/gitlab/-/issues/543982+ - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/194906+ <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->