Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ref/ci: --fetch-depth #364

Merged
merged 1 commit into from
Nov 1, 2022
Merged

ref/ci: --fetch-depth #364

merged 1 commit into from
Nov 1, 2022

Conversation

casperdcl
Copy link
Contributor

@casperdcl casperdcl commented Nov 1, 2022

@shcheklein shcheklein temporarily deployed to cml-dev-ci-fetch-depth-osyqteo November 1, 2022 00:26 Inactive
@casperdcl casperdcl requested a review from a team November 1, 2022 00:27
@casperdcl casperdcl self-assigned this Nov 1, 2022
@casperdcl casperdcl added documentation Markdown files C: ref Content of /doc/*-reference labels Nov 1, 2022
@github-actions
Copy link

github-actions bot commented Nov 1, 2022

438d9d9

Link Check Report

There were no links to check!

CML watermark

Copy link
Member

@0x2b3bfa0 0x2b3bfa0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why recommend cml ci --fetch-depth=0 though?

Comment on lines -29 to +28
$ cml ci
$ cml ci --fetch-depth=0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Product Q: Should it be the default value?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no default value for this option, Imagine that 95% of the use cases will be --fetch-depth=0 or the previous alias for this --unshallow

Copy link
Contributor Author

@casperdcl casperdcl Nov 1, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--fetch-depth=0 is slow & space-consuming so can't be the default. Also, we can't use --fetch-depth=1 imitating GHA because that would truncate unshallow repos.

Safest is to have undefined (unset) default, i.e. do-nothing, but document --fetch-depth=0 as the most likely use case.

@casperdcl casperdcl merged commit 05baa36 into master Nov 1, 2022
@casperdcl casperdcl deleted the ci-fetch-depth branch November 1, 2022 22:01
@github-actions
Copy link

github-actions bot commented Nov 1, 2022

05baa36

Link Check Report

There were no links to check!

@jorgeorpinel jorgeorpinel changed the title ref/ci: --fetch-depth ref/ci: --fetch-depth Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: ref Content of /doc/*-reference documentation Markdown files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants