ROX-13648: check out full history

[porridge]

Description

The ability to see at least some history is crucial for the logic in terraforming script which selects the commit from which to retrieve the id to use as the image tag name.

It's easier to just fetch the whole history than to come up with some arbitrary threshold number.
Relevant section of docs for the checkout action.

Checklist (Definition of Done)

• Unit and integration tests added
• Added test description under Test manual
• Evaluated and added CHANGELOG.md entry if required
• Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
• CI and all relevant tests are passing
• Add the ticket number to the PR title if available, i.e. ROX-12345: ...
• Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.

Test manual

No real way to test this. 😢

[kovayur]

Do we really need this for stage?

[porridge]

Strictly speaking we don't, but I'd really like to keep differences between stage and prod to absolutely necessary minimum. Let me add a comment.

[kovayur]

No real way to test this. 😢

Can we at least create a test branch X, add some simple GH workflow there and merge branch Y into X to ensure that the problematic git command is executed as intended?

UPD: Or maybe just push changes to trigger the test workflow, without merging

[porridge]

No real way to test this. cry

Can we at least create a test branch X, add some simple GH workflow there and merge branch Y into X to ensure that the problematic git command is executed as intended?

• Run on a linear history, shows the hash returned matches HEAD
• Run on a merge commit, shows the hash returned matches the dummy commit id. We were even lucky to have GitHub create another merge commit on top, to keep in sync with the PR base :-)

[porridge]

/retest

[kovayur]

Good job, special thanks for performing tests.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kovayur, porridge

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 [kovayur,porridge]

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