Backport #2

[carlopi]

Copy of #2.

There were some issue with the actions used underneath, that should now be fixed via duckdb/extension-ci-tools#46.

Thanks for the patience, I suppose this should now work (as it should also close and reopen the previous PR).
Tested on a fork at https://github.com/carlopi/duckdb-extension-clickhouse-sql/actions/runs/9853610199/job/27204552083

[carlopi]

Either this or #2 will fix #1.

@lmangani, thanks for iterating on this, we uncovered a couple of problems in our setup.

[lmangani]

Thanks @carlopi for taking the time to assist!
The PR action both worked AND failed 😆 trying to understand the discrepancy

[lmangani]

I can't understand - Since actions succeed I guess we can merge this PR and deal with the results directly in the main branch

[carlopi]

Magic of GitHub, I think this is good to merge, I think the other failures where connected at the original commit, since GitHub can't see there is some hidden state where now the proper action is run.

Thanks for bearing with this / experimenting on this.

[lmangani]

I really appreciate the help @carlopi! Next I need to learn how to submit this to the community repo!
Is there an action to support that workflow or it just needs a pointer? In which case... also need to learn where builds need to be

[carlopi]

This is a PR that just got merged: duckdb/community-extensions#38, you can take a look for inspiration.

Basically you need to add a description.yml file in a folder called as your extension, fields that are most relevant are: which github repository to build against AND which commit.
Plus name / description, and optionally example and extended description.

I am going to write some more proper docs.