7.0.1

What's Changed

• Clean up unused stuff in E2E tests by @ofalvai in #200
• Add option for unlimited clone depth by @ofalvai in #201

Full Changelog: 7.0.0...7.0.1

7.0.0: Shallow clone by default

Highlights

The step now tries to do a shallow clone of the repository by default (instead of fetching the entire history) to speed up clones.

This means that you no longer need to define the clone_depth input, it's only used for overriding the default behavior. By default, the step will shallow-fetch (depth=1) in all cases except for PR builds where the PR merge reference is not available. In this case, it fetches the last 50 commits and merges the PR branch into the target branch manually. You can use the clone_depth input to set a higher depth value if needed.

Breaking changes and migration

• The step no longer fetches the entire repo history: if you have custom scripts or steps that rely on the commit history (or the git log command), you might want to set a custom clone_depth value.
• Removed manual_merge input: this is no longer needed because the step prefers fetching the merge ref or the patch file and only does a manual merge if the former is not available.
• Fixed incorrect spelling of output names: GIT_CLONE_COMMIT_COMMITTER_NAME, GIT_CLONE_COMMIT_COMMITTER_EMAIL
• Removed PR_ID input, although it didn't have any effect on the behavior.

What's Changed

• Use v2 stepconf parser in #189
• Remove manual_merge input, only do it as a fallback in #188
• Refactor output exports in #190
• Replace usage of COMMITER with COMMITTER in #192
• Add method for determining the ideal default clone depth based if the… in #191
• Use PR head ref in output export in #193
• Disable git GC before fetch #194
• Reorder inputs and categories in #195
• Remove PR ID input in #196
• Better step input descriptions in #197

Full Changelog: 6.2.3...7.0.0

6.2.3

What's Changed

• Improve checkout method documentation by @ofalvai in #187
• Fix merge ref checkout by @ofalvai in #186

Full Changelog: 6.2.2...6.2.3

6.2.2

What's Changed

• Log checkout metrics by @ofalvai in #185

Full Changelog: 6.2.1...6.2.2

6.2.1

What's Changed

• Revert "Remove run-if condition (#179)" by @hisaac in #180

Full Changelog: 6.2.0...6.2.1

6.2.0

What's Changed

• Use custom bot token in stale workflow by @ofalvai in #171
• Configure Renovate by @renovate in #173
• Apply YAML lint by @ofalvai in #175
• Update filedownloader package by @lpusok in #178
• Remove run_if condition to allow for use in non-CI environments by @hisaac in #179

New Contributors

• @renovate made their first contribution in #173
• @hisaac made their first contribution in #179

Full Changelog: 6.1.2...6.1.3

6.1.2

[#170] Mark Git LFS as a step dependency to avoid a missing dependency in the future

6.1.1

Fixed a bug when a failure during fetch was not handled properly and mistakenly presented the step's run as success

6.1.0

Will correctly export commit author, hash and other outputs for PR builds.
Previously this was not always the case, and the commit information was output for a temporary merge commit (author: J. Doe).
From now the commit by the PR author from the source (head) branch will be used.

The outputs are not exported for PR builds if using hosted Bitbucket with the Manual merge input set to no. (In this case the the commit by the PR author is not available).

Outputs exported for PR builds:
GIT_CLONE_COMMIT_AUTHOR_NAME, GIT_CLONE_COMMIT_AUTHOR_EMAIL, GIT_CLONE_COMMIT_HASH, GIT_CLONE_COMMIT_MESSAGE_SUBJECT, GIT_CLONE_COMMIT_MESSAGE_BODY
Outputs not exported for PR builds:
GIT_CLONE_COMMIT_COMMITER_NAME, GIT_CLONE_COMMIT_COMMITER_EMAIL, GIT_CLONE_COMMIT_COUNT

6.0.0

Version 6.0.0 replaces the limit_submodule_update_depth input by the submodule_update_depth input, which can be used to specify the depth of the submodule update command.

The submodule_update_depth is only applied if it is greater than 0 and update_submodules is set to "yes".

Related pull requests

• submodule update depth made configurable (#161)