What were you trying to do that didn't work?

Git v2.49.0 introduced the revision flag to the "clone" command, which when combined with the depth flag allows developers to set up an effective shallow clone of a repository by commit SHA. This is a common occurrence in CI/CD systems that trigger builds using webhooks.

This is currently not available in CentOS Stream 10 - the current git version (v2.47.z) does not have this feature.

What is the impact of this issue to you?

In Shipwright, we default to shallow clones when a build references a branch or tag. However, we cannot do this if the build specifies a full commit SHA as its revision. This leads to behavior skews in our API (a branch, tag, or SHA can be specified in the `revision` field). See BUILD-1424.

The upstream community currently uses UBI 10 as their base container images, and would like to continue to stay on UBI. See https://github.com/shipwright-io/build/issues/1874

Please provide the package NVR for which the bug is seen:

git v2.47.3

How reproducible is this bug?:

Always

Steps to reproduce

1. Execute:

   git clone --depth 1 --revision <commit SHA> ...
   

Expected results

git clone command succeeds, with shallow/pruned history

Actual results

git clone command fails: revision flag does not exist