switch to extension-ci-tools based CI #15
Merged
Conversation
This file contains 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
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.
With this PR, duckdb-prql should be good to go for going into the community extensions repo.
I switched a few things around to stay in line with the most recent extension template. This simplifies things a little bit and should ensure that when CI passes in this repo, it will pass in the the community extensions repo.
@ywelsch I'm not able to test the deploy side of things here: I think it works? Ofcourse you could consider completely stripping the manual deploy in favor of the community extensions repo, but maybe having your own deploy step is nice as it give you nightly binaries to try out easily before PR-ing updates into community extensions.