Merge branch 'main' into shuowei-job-history

Author: shuoweil

.gemini/common/constraints.md

@@ -0,0 +1,8 @@
+## Constraints
+
+- Only add git commits. Do not change git history.
+- Follow the spec file for development.
+  - Check off items in the "Acceptance
+    criteria" and "Detailed steps" sections with `[x]`.
+  - Please do this as they are completed.
+  - Refer back to the spec after each step.

.gemini/common/docs.md

@@ -0,0 +1,9 @@
+## Documentation
+
+If a method or property is implementing the same interface as a third-party
+package such as pandas or scikit-learn, place the relevant docstring in the
+corresponding `third_party/bigframes_vendored/package_name` directory, not in
+the `bigframes` directory. Implementations may be placed in the `bigframes`
+directory, though.
+
+@../tools/test_docs.md

GEMINI.md .gemini/tasks/scalar_op.mdGEMINI.md renamed to .gemini/tasks/scalar_op.md

@@ -1,75 +1,4 @@
-# Contribution guidelines, tailored for LLM agents
-
-## Testing
-
-We use `nox` to instrument our tests.
-
-- To test your changes, run unit tests with `nox`:
-
-  ```bash
-  nox -r -s unit
-  ```
-
-- To run a single unit test:
-
-  ```bash
-  nox -r -s unit-3.13 -- -k <name of test>
-  ```
-
-- Ignore this step if you lack access to Google Cloud resources. To run system
-  tests, you can execute::
-
-   # Run all system tests
-   $ nox -r -s system
-
-   # Run a single system test
-   $ nox -r -s system-3.13 -- -k <name of test>
-
-- The codebase must have better coverage than it had previously after each
-  change. You can test coverage via `nox -s unit system cover` (takes a long
-  time). Omit `system` if you lack access to cloud resources.
-
-## Code Style
-
-- We use the automatic code formatter `black`. You can run it using
-  the nox session `format`. This will eliminate many lint errors. Run via:
-
-  ```bash
-  nox -r -s format
-  ```
-
-- PEP8 compliance is required, with exceptions defined in the linter configuration.
-  If you have ``nox`` installed, you can test that you have not introduced
-  any non-compliant code via:
-
-  ```
-  nox -r -s lint
-  ```
-
-- When writing tests, use the idiomatic "pytest" style.
-
-## Documentation
-
-If a method or property is implementing the same interface as a third-party
-package such as pandas or scikit-learn, place the relevant docstring in the
-corresponding `third_party/bigframes_vendored/package_name` directory, not in
-the `bigframes` directory. Implementations may be placed in the `bigframes`
-directory, though.
-
-### Testing code samples
-
-Code samples are very important for accurate documentation. We use the "doctest"
-framework to ensure the samples are functioning as expected. After adding a code
-sample, please ensure it is correct by running doctest. To run the samples
-doctests for just a single method, refer to the following example:
-
-```bash
-pytest --doctest-modules bigframes/pandas/__init__.py::bigframes.pandas.cut
-```
-
-## Tips for implementing common BigFrames features
-
-### Adding a scalar operator
+## Adding a scalar operator
 
 For an example, see commit
 [c5b7fdae74a22e581f7705bc0cf5390e928f4425](https://github.com/googleapis/python-bigquery-dataframes/commit/c5b7fdae74a22e581f7705bc0cf5390e928f4425).
@@ -136,13 +65,3 @@ To add a new scalar operator, follow these steps:
     - If you are overriding a pandas or GeoPandas property, add a unit test to
       ensure the correct behavior (e.g., raising `NotImplementedError` if the
       functionality is not supported).
-
-
-## Constraints
-
-- Only add git commits. Do not change git history.
-- Follow the spec file for development.
-  - Check off items in the "Acceptance
-    criteria" and "Detailed steps" sections with `[x]`.
-  - Please do this as they are completed.
-  - Refer back to the spec after each step.

.gemini/tools/style_nox.md

@@ -0,0 +1,18 @@
+## Code Style with nox
+
+- We use the automatic code formatter `black`. You can run it using
+  the nox session `format`. This will eliminate many lint errors. Run via:
+
+  ```bash
+  nox -r -s format
+  ```
+
+- PEP8 compliance is required, with exceptions defined in the linter configuration.
+  If you have ``nox`` installed, you can test that you have not introduced
+  any non-compliant code via:
+
+  ```
+  nox -r -s lint
+  ```
+
+- When writing tests, use the idiomatic "pytest" style.

.gemini/tools/test_docs.md

@@ -0,0 +1,10 @@
+## Testing code samples
+
+Code samples are very important for accurate documentation. We use the "doctest"
+framework to ensure the samples are functioning as expected. After adding a code
+sample, please ensure it is correct by running doctest. To run the samples
+doctests for just a single method, refer to the following example:
+
+```bash
+pytest --doctest-modules bigframes/pandas/__init__.py::bigframes.pandas.cut
+```

.gemini/tools/test_nox.md

@@ -0,0 +1,28 @@
+## Testing with nox
+
+Use `nox` to instrument our tests.
+
+- To test your changes, run unit tests with `nox`:
+
+  ```bash
+  nox -r -s unit
+  ```
+
+- To run a single unit test:
+
+  ```bash
+  nox -r -s unit-3.14 -- -k <name of test>
+  ```
+
+- Ignore this step if you lack access to Google Cloud resources. To run system
+  tests, you can execute::
+
+   # Run all system tests
+   $ nox -r -s system
+
+   # Run a single system test
+   $ nox -r -s system-3.14 -- -k <name of test>
+
+- The codebase must have better coverage than it had previously after each
+  change. You can test coverage via `nox -s unit system cover` (takes a long
+  time). Omit `system` if you lack access to cloud resources.

.gemini/tools/test_pytest.md

@@ -0,0 +1,9 @@
+## Testing with pytest
+
+Use `pytest` to instrument our tests.
+
+- To test your changes, run `pytest`:
+
+  ```bash
+  pytest <test_file>::<test_case>
+  ```

.github/CODEOWNERS

@@ -5,8 +5,8 @@
 # https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-syntax
 # Note: This file is autogenerated. To make changes to the codeowner team, please update .repo-metadata.json.
 
-# @googleapis/yoshi-python @googleapis/api-bigquery-dataframe are the default owners for changes in this repo
-*     @googleapis/yoshi-python @googleapis/api-bigquery-dataframe
+# @googleapis/cloud-sdk-python-team @googleapis/bigquery-dataframe-team are the default owners for changes in this repo
+*     @googleapis/cloud-sdk-python-team @googleapis/bigquery-dataframe-team
 
-# @googleapis/python-samples-reviewers @googleapis/api-bigquery-dataframe are the default owners for samples changes
-/samples/   @googleapis/python-samples-reviewers @googleapis/api-bigquery-dataframe
+# @googleapis/python-samples-reviewers @googleapis/bigquery-dataframe-team are the default owners for samples changes
+/samples/   @googleapis/python-samples-reviewers @googleapis/bigquery-dataframe-team

.github/blunderbuss.yml

@@ -4,14 +4,14 @@
 # Note: This file is autogenerated. To make changes to the assignee
 # team, please update `codeowner_team` in `.repo-metadata.json`.
 assign_issues:
-  - googleapis/api-bigquery-dataframe
+  - googleapis/bigquery-dataframe-team
 
 assign_issues_by:
   - labels:
       - "samples"
     to:
       - googleapis/python-samples-reviewers
-      - googleapis/api-bigquery-dataframe
+      - googleapis/bigquery-dataframe-team
 
 assign_prs:
-  - googleapis/api-bigquery-dataframe
+  - googleapis/bigquery-dataframe-team

.github/workflows/docs.yml

@@ -36,6 +36,3 @@ jobs:
       run: |
         python -m pip install --upgrade setuptools pip wheel
         python -m pip install nox
-    - name: Run docfx
-      run: |
-        nox -s docfx