Do not fail Vendor.yml when no changes imported#220
Merged
staticlibs merged 1 commit intoduckdb:mainfrom May 12, 2025
Merged
Conversation
This change improves the check in the DuckDB engine sources vendoring process. If no changes are detected in the incoming sources then the remaining of the `Vendor.yml` job is skipped instead of moving it to "Failure" state. Testing: debugged this in a separate repo.
staticlibs
added a commit
to staticlibs/duckdb-odbc
that referenced
this pull request
May 12, 2025
This change improves the check in the DuckDB engine sources vendoring process. If no changes are detected in the incoming sources then the remaining of the Vendor.yml job is skipped instead of moving it to "Failure" state. Testing: this logic was debugged in duckdb/duckdb-java#220.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change improves the check in the DuckDB engine sources vendoring process. If no changes are detected in the incoming sources then the remaining of the
Vendor.ymljob is skipped instead of moving it to "Failure" state.Testing: debugged this in a separate repo.