<!--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> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=602558) </details> <!--IssueSummary end--> ## Context There are a couple of session piling up in the GitLab monolith where duo developer runs into git operation problems, e.g.: * https://gitlab.com/gitlab-org/gitlab/-/automate/agent-sessions/4280870 * https://gitlab.com/gitlab-org/gitlab/-/automate/agent-sessions/4292377 * https://gitlab.com/gitlab-org/gitlab/-/automate/agent-sessions/4295447 The issues are of different nature but alway occur in combination with git commands. We should investigate the root cause of those and decide how to fix it. ## Potential hints Maybe related: Currently, we are shallow cloning repositories for the flow runner. In our Duo Developer flow we have a dedicated step that unshallows the repository. On big repos like GitLab, this often times out or runs into Gitaly issues. There was an idea to allow proper cloning upfront to avoid those types of issues https://gitlab.com/gitlab-org/gitlab/-/work_items/601045.