pull_requests

Table actions

3 rows where user = 13254278

✖
✖

✎ 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
425094701 MDExOlB1bGxSZXF1ZXN0NDI1MDk0NzAx 4109 closed 0 Add xarray-custom to related projects astropenguin 13254278 We have released [xarray-custom](https://github.com/astropenguin/xarray-custom), a Python package which helps to create custom DataArray in the same manner as [the Python's native dataclass](https://docs.python.org/3/library/dataclasses.html). This PR adds the project to the "Extend xarray capabilities" section in `doc/related-projects.rst`. It would be appreciated if you could merge it (if this PR fits the purpose of the xarray documentation). 2020-05-29T13:11:35Z 2020-05-29T17:26:37Z 2020-05-29T16:50:59Z 2020-05-29T16:50:59Z a2e9804d372a2e8a0d83904544b1d8421bfa2b44     0 19338d1c36ea4d2255c78855df6bc8b8b2c25c92 e5cc19cd8f8a69e0743f230f5bf51b7778a0ff96 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/4109  
474526976 MDExOlB1bGxSZXF1ZXN0NDc0NTI2OTc2 4382 closed 0 Add xarray-compare to related projects astropenguin 13254278 We have released [xarray-compare](https://github.com/astropenguin/xarray-compare), a Python package which provides extra data-comparison features (e.g., `dataarray.isbetween(lower, upper)`). This PR adds the project to the "Extend xarray capabilities" section in `doc/related-projects.rst`. We have a concern: This package **directly** adds some methods to `xarray.DataArray` by using [the accessor feature](https://xarray.pydata.org/en/stable/internals.html#extending-xarray). For example, `dataarray.isbetween()` is implemented by registering an accessor whose name is `'isbetween'`. This usage may not be what is expected by the xarray's developers. So it would be appreciated if you could merge it, but if you feel that it does not fit the docs, please reject the PR. Thank you! 2020-08-27T08:05:42Z 2020-09-04T20:08:11Z 2020-09-04T20:08:10Z 2020-09-04T20:08:10Z a6eccfa346b14d83a745cdbfe4718d8c046c5e12     0 dedce9772f5ed3b21318324402d2fe769a9e6587 9c85dd5f792805bea319f01f08ee51b83bde0f3b CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/4382  
717165281 MDExOlB1bGxSZXF1ZXN0NzE3MTY1Mjgx 5725 closed 0 Add xarray-dataclasses to ecosystem in docs astropenguin 13254278 We have released [xarray-dataclasses](https://github.com/astropenguin/xarray-dataclasses), an xarray extension for typed DataArray and Dataset creation. This PR added the project to the "Extend xarray capabilities" section in `doc/ecosystem.rst`. Plus we removed [xarray-custom](https://github.com/astropenguin/xarray-custom) (added by #4109) from the same section. This is because it is not maintained and xarray-dataclasses is the successor. It would be appreciated if you could merge it (if this PR fits the purpose of the xarray documentation). 2021-08-21T15:07:08Z 2021-08-21T15:52:13Z 2021-08-21T15:28:31Z 2021-08-21T15:28:31Z 48a9dbe7d8dc2361bc985dd9fb1193a26135b310     0 92639b7b51a44d28fe59ef05b7297c464d04fced 1434b8d04c5d6d07472dc9997a589353e7da4b06 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/5725  

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]);