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

fix: fetch all git references in publish-cli workflow - MERGEOK #32287

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

esolitos
Copy link
Contributor

@esolitos esolitos commented Aug 28, 2024

What

In the "Publish CLI" action adds the fetch-depth: 0 option to the checkout github actions.

Why

The deploy process does a check to see if there has been any changes in the codebase, but with a shallow clone it cannot do that, by setting fetch-depth: 0 the GH Action will fetch also all references.


I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@esolitos esolitos changed the title fix: fetch all git references in publish-cli workflow fix: fetch all git references in publish-cli workflow - MERGEOK Aug 28, 2024
@esolitos esolitos self-assigned this Aug 28, 2024
@esolitos esolitos marked this pull request as ready for review August 28, 2024 07:21
@bjormel bjormel merged commit 0ee8a6b into master Aug 28, 2024
6 checks passed
@bjormel bjormel deleted the esolitos-patch-3 branch August 28, 2024 08:10
@freva
Copy link
Member

freva commented Aug 28, 2024

Please observe merge stops even for changes that don't affect the build because each merge to this repo triggers a new Vespa version build followed by all the system/performance/integration tests that take a few hours to run, this means that when a fix (for the issue that caused the merge stop) is merged, it may take longer to get it out, which makes the merge stop even longer :)

@esolitos
Copy link
Contributor Author

Good to know, sorry about that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants