When a full commit SHA is provided as revision, provide it with the git clone command and honor the depth

[SaschaSchwarze0]

Changes

Fixes #1874

When providing a commit sha as revision of a Git source, then we always performed a git clone --no-checkout followed by a git checkout COMMIT_SHA. By doing that, we performed a full history clone and therefore ignored the depth provided by the user.

In case the commit sha is a full commit sha, we can actually provide it with git clone --revision COMMIT_SHA and then also honor the deptch. For a short commit sha, this is not working, there we must still clone the full history to be able to checkout the short sha afterwards.

However, our ubi9-based images do not contain a Git binary that is new enough to support the --revision flag:

2025/05/11 09:34:31 /usr/bin/git -c safe.directory=/workspace/source clone --quiet --no-tags --revision 0be20591d7096bef165949c22f6059f5d8eb6a85 --depth 1 -- https://github.com/shipwright-io/sample-nodejs /workspace/source
2025/05/11 09:34:31 error: unknown option `revision'

Therefore, that optimized approach is only used when --revision is available.

The existing unit tests cover both cases (full and short sha) already.

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

When specifying a Git source with a revision value which is a full commit SHA, then the source step now clones the repository at that point with the provided `depth` (default 1). Previously, when the revision was a commit SHA, it has always cloned the full history. This continues to be the case when you provide a short commit SHA. Note that this new approach is only used if Git supports the `revision` flag on `git clone`. This is not the case with the ubi9-based images that Shipwright provides.

[qu1queee]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qu1queee]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment