@@ -22,7 +22,7 @@ Conduct](https://github.com/adbc-drivers/databricks?tab=coc-ov-file#readme).
2222## Reporting Issues and Making Feature Requests
2323
2424Please file issues and feature requests on the GitHub issue tracker:
25- https://github.com/adbc-drivers/google /issues
25+ https://github.com/adbc-drivers/databricks /issues
2626
2727Potential security vulnerabilities should be reported to
2828[ security@adbc-drivers.org ] ( mailto:security@adbc-drivers.org ) instead. See
3131
3232## Build and Test
3333
34- ### Golang
34+ ### C#
3535
36- For basic development, the driver can be built and tested like any Go project.
37- From the ` go /` subdirectory:
36+ For basic development, the driver can be built and tested like any .NET
37+ project. From the ` csharp /` subdirectory:
3838
3939``` shell
40- $ go build ./...
41- $ go test -tags assert -v ./...
40+ $ dotnet build
41+ $ dotnet test
4242```
4343
44- This will not produce a shared library, however; that requires invoking the
45- full build script. You will need [ pixi] ( https://pixi.sh/ ) installed. From
46- the ` go/ ` subdirectory:
47-
48- ``` shell
49- $ pixi run make
50- ```
51-
52- To run the validation suite, you will first need to build the shared library.
53- You will also need to set up a BigQuery instance (see [ the validation
54- README] ( ./validation/README.md ) ). Finally, from the ` go/validation/ `
55- subdirectory:
56-
57- ``` shell
58- $ pixi run test
59- ```
60-
61- This will produce a test report, which can be rendered into a documentation
62- page (using MyST Markdown):
63-
64- ``` shell
65- $ pixi run gendocs --output generated/
66- ```
67-
68- Then look at ` ./generated/bigquery.md ` .
69-
7044## Opening a Pull Request
7145
7246Before opening a pull request:
@@ -85,14 +59,14 @@ When writing the pull request description:
8559
8660- Ensure the title follows [ Conventional
8761 Commits] ( https://www.conventionalcommits.org/en/v1.0.0/ ) format. The
88- component should be ` go ` if it affects the Go driver, or it can be omitted
89- for general maintenance (in general: it should be a directory path relative
90- to the repo root, e.g. ` go /auth` would also be valid if that directory
91- existed). Example titles:
62+ component should be ` csharp ` if it affects the C# driver, or it can be
63+ omitted for general maintenance (in general: it should be a directory path
64+ relative to the repo root, e.g. ` csharp /auth` would also be valid if that
65+ directory existed). Example titles:
9266
93- - ` feat(go ): support GEOGRAPHY data type `
67+ - ` feat(csharp ): support GEOGRAPHY data type `
9468 - ` chore: update action versions `
95- - ` fix!(go ): return us instead of ms `
69+ - ` fix!(csharp ): return us instead of ms `
9670
9771 Ensure that breaking changes are appropriately flagged with a ` ! ` as seen
9872 in the last example above.
0 commit comments