Retry a full clone when git server does not support shallow capabilities

[llenk]

What was the end-user or developer problem that led to this PR?

#7547

What is your fix for the problem, implemented in this PR?

The depth arguments in the git command were causing the problem. If we get the error on the first try, we remove the depth arguments from the command and try again.

Make sure the following tasks are checked

• Describe the problem / feature
• Write tests for features and bug fixes
• Write code to solve the problem
• Make sure you follow the current code style and write meaningful commit messages without tags

[welcome]

Thanks for opening a pull request and helping make RubyGems and Bundler better! Someone from the RubyGems team will take a look at your pull request shortly and leave any feedback. Please make sure that your pull request has tests for any changes or added functionality.

We use GitHub Actions to test and make sure your change works functionally and uses acceptable conventions, you can review the current progress of GitHub Actions in the PR status window below.

If you have any questions or concerns that you wish to ask, feel free to leave a comment in this PR or join our #rubygems or #bundler channel on Slack.

For more information about contributing to the RubyGems project feel free to review our CONTRIBUTING guide

[martinemde]

@llenk thank you! It was great working with you at RailsConf.

[deivid-rodriguez]

Added a minor style comment but looks good to me other than that.

[martinemde]

I like the revisions. Looks more general now. Maybe even a pattern to follow if there's other ways to back off the command when it doesn't work.

[simi]

🤔 IMHO best would be to be able to check if remote supports "shallow capabilities", but I wasn't able to find out generic way to find out.

[simi]

@llenk would you mind to squash commits please before merge?

[deivid-rodriguez]

🤔 IMHO best would be to be able to check if remote supports "shallow capabilities", but I wasn't able to find out generic way to find out.

I was considering that, but (in addition to not being obvious how to do it) since most servers these days support them, it felt better to optimize for that case, and react when servers don't support it, instead of detecting support upfront.

[deivid-rodriguez]

Thanks for the great work here!

[martinemde]

Oops, I didn't notice it wasn't squashed yet. It's only 1 extra commit so I won't feel too bad 😉