pull_requests

Table actions

2 rows where user = 3460034

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date), merged_at (date)

id ▼ node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
329017956 MDExOlB1bGxSZXF1ZXN0MzI5MDE3OTU2 3410 closed 0 Update Terminology page to account for multidimensional coordinates jthielen 3460034 As discussed in https://github.com/pydata/xarray/pull/3352, this PR modifies the Terminology page in the docs to briefly address multidimensional coordinates. Sorry for the delay in getting this in! Also, when attempting to test the doc build, I found that the `doc/environment.yml` file was no longer present, so I updated it to `ci/requirements/doc.yml`. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API 2019-10-17T00:52:12Z 2019-10-24T04:25:43Z 2019-10-24T04:25:43Z 2019-10-24T04:25:43Z 35c75f557a510b7e81c70fcaad8cad419a12ee2e     0 98044fb322ce167a3a3e262acc18869260b408a3 b0c336f6b4b8d425e5c89d6f75f561823806137b CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/3410  
1197041777 PR_kwDOAMm_X85HWWhx 7437 open 0 DRAFT: Implement `open_datatree` in BackendEntrypoint for preliminary DataTree support jthielen 3460034 <!-- Feel free to remove check-list items aren't relevant to your change --> As discussed among folks at today's Pangeo working meeting (cc @jhamman, @TomNicholas), we are looking to try adding support for `DataTree` in the Backend API, so that backend engines can readily add `DataTree` capability. For example, with `cfgrib`, we could have ```python import xarray as xr dt = xr.open_datatree("path/to/gribfile.grib", engine="cfgrib") ``` given that `cfgrib` implements the appropriate method to their `BackendEntrypoint` subclass. Similarly, with NetCDF files or Zarr stores with groups, we could open as `DataTree` to obviate the need to specify a single group. Working Design Doc: https://hackmd.io/Oqeab-54TqOOHd5FdCb5DQ?edit xref https://github.com/ecmwf/cfgrib/issues/327, https://github.com/openradar/xradar/issues/7 - ~~Closes #xxxx~~ - [ ] Tests added - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` 2023-01-13T17:17:41Z 2023-07-31T10:09:18Z     4210ae92dbfaf917c5b5ebc7e30754936f87a258     1 9d64b3657142474d99d2cfbb1b1db6a56ae324f3 3ee7b5a63bb65ce62eff3dafe4a2e90bca7a9eeb CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/7437  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [pull_requests] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [state] TEXT,
   [locked] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [body] TEXT,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [merged_at] TEXT,
   [merge_commit_sha] TEXT,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [draft] INTEGER,
   [head] TEXT,
   [base] TEXT,
   [author_association] TEXT,
   [auto_merge] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_pull_requests_merged_by]
    ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
    ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
    ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
    ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
    ON [pull_requests] ([user]);