chore: update to repo standards (#5)

Author: lidavidm

.github/dependabot.yaml

@@ -0,0 +1,39 @@
+# Copyright (c) 2026 ADBC Drivers Contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+version: 2
+updates:
+  - package-ecosystem: "cargo"
+    commit-message:
+      prefix: "chore: "
+    directory: "/"
+    groups:
+      arrow-adbc:
+        applies-to: version-updates
+        patterns:
+          - "arrow-*"
+          - "adbc_*"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    commit-message:
+      prefix: "chore: "
+    directory: "/"
+    groups:
+      actions:
+        patterns:
+          - "*"
+    schedule:
+      interval: "weekly"

CONTRIBUTING.md

@@ -0,0 +1,93 @@
+<!--
+  Copyright (c) 2026 ADBC Drivers Contributors
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+          http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+# How to Contribute
+
+All contributors are expected to follow the [Code of
+Conduct](https://github.com/adbc-drivers/clickhouse?tab=coc-ov-file#readme).
+
+## Reporting Issues and Making Feature Requests
+
+Please file issues and feature requests on the GitHub issue tracker:
+https://github.com/adbc-drivers/clickhouse/issues
+
+Potential security vulnerabilities should be reported to
+[security@adbc-drivers.org](mailto:security@adbc-drivers.org) instead.  See
+the [Security
+Policy](https://github.com/adbc-drivers/clickhouse?tab=security-ov-file#readme).
+
+## Build and Test
+
+Most likely, you want to contribute to the upstream driver at
+https://github.com/ClickHouse/adbc_clickhouse.  This repository only holds
+build and test scripts for the ADBC Driver Foundry.
+
+You can invoke the build script used by CI:
+
+```shell
+$ cd src/
+# ./ci/scripts/build.sh <test|release> <linux|macos|windows> <amd64|arm64>
+# For example, this makes a debug build:
+$ ./ci/scripts/build.sh test linux amd64
+```
+
+This will produce a shared library in `src/build`.
+
+To run the validation suite, you will first need to build the shared library.
+You will also need to set up a ClickHouse instance (see [the validation
+README](./src/validation/README.md)).  Finally, from the `src/` subdirectory:
+
+```shell
+$ pixi run validate
+```
+
+This will produce a test report, which can be rendered into a documentation
+page (using MyST Markdown):
+
+```shell
+$ pixi run gendocs --output generated/
+```
+
+Then look at `./generated/clickhouse.md`.
+
+## Opening a Pull Request
+
+Before opening a pull request:
+
+- Review your changes and make sure no stray files, etc. are included.
+- Ensure the Apache license header is at the top of all files.
+- Check if there is an existing issue.  If not, please file one, unless the
+  change is trivial.
+- Assign the issue to yourself by commenting just the word `take`.
+- Run the static checks by installing [pre-commit](https://pre-commit.com/),
+  then running `pre-commit run --all-files` from inside the repository.  Make
+  sure all your changes are staged/committed (unstaged changes will be
+  ignored).
+
+When writing the pull request description:
+
+- Ensure the title follows [Conventional
+  Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.  The
+  component generally be omitted.  Example titles:
+
+  - `feat: support GEOGRAPHY data type`
+  - `chore: update action versions`
+  - `fix!: return us instead of ms`
+
+  Ensure that breaking changes are appropriately flagged with a `!` as seen
+  in the last example above.
+- Make sure the description ends with `Closes #NNN`, `Fixes #NNN`, or
+  similar, so that the issue will be linked to your pull request.

src/validation/CLAUDE.md

@@ -24,12 +24,14 @@ Get validation tests passing using `pixi run validate`. Use `-k` to run a single
 
 ### Query-based tests (type/select, type/literal, type/bind, ingest)
 
-1. **Override queries**: If ClickHouse requires different SQL syntax, create override query files in `./validation/queries/` using the `.txtcase` format.
+1. **Override queries**: If ClickHouse requires different SQL syntax, create override query files in `./validation/queries/` using the `.txtcase` format.  Do not override sections that are identical to the base query.  When overriding, check the documentation for the database and add `tags.sql-type-name` to the TOML metadata to reflect the "canonical" type name for that data type.  Also, if data values need to be changed, make sure "extreme" values are tested.  For example, timestamps/datetimes should test the ANSI SQL extremes of 0001-01-01 and 9999-12-31, or if not possible, they should test the extremes of the database.
 
 2. **Mark as broken**: If a test cannot pass due to driver or vendor limitations, add to the metadata section:
    - `[tags] broken-driver = "reason"` - for driver limitations
    - `[tags] broken-vendor = "reason"` - for ClickHouse limitations
 
+   For ClickHouse limitations, try to link to database documentation.
+
 3. **Hide tests**: Use `hide = true` in metadata to completely hide irrelevant tests.
 
 ### Non-query tests (connection, statement)

src/validation/README.md

@@ -0,0 +1,27 @@
+<!--
+  Copyright (c) 2026 ADBC Drivers Contributors
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+          http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+# Validation Suite Setup
+
+You must set up a ClickHouse instance.  The included [Docker
+Compose](https://docs.docker.com/compose/) config can be used:
+
+```
+$ cd src/
+$ docker compose up
+```
+
+This will start ClickHouse running on `http://localhost:8123`.