pull_requests
2 rows where user = 57705593
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 830156720 | PR_kwDOAMm_X84xey-w | 6187 | closed | 0 | to_netcdf: docstrings for compute parameter | tovogt 57705593 | As discussed in #6174, closing and re-opening a file between calls of to_netcdf can be avoided by using `compute=False`. In case of many write operations on the same file (e.g. for many separate groups in a netCDF4 file), this often improves the performance significantly. This PR makes note of this effect in the docstrings so that users can learn about it without diving into the source code. - Unfortunately, it doesn't close #6174, because that issue also discusses the problem of obtaining a full list of all groups contained within a netCDF4 file when *reading* from that file. - Changes to the doc strings are not mentioned in `whats-new.rst`, are they? | 2022-01-24T09:14:01Z | 2023-09-14T04:36:06Z | 2023-09-14T04:36:06Z | 2191aed6f339f010b8ef14f4c777f624f6bc4cf2 | 0 | a30eb938b4498b5f82eba6dbef63a4954b622d07 | d1e4164f3961d7bbb3eb79037e96cae14f7182f8 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6187 | |||||
| 881324401 | PR_kwDOAMm_X840h_Fx | 6366 | closed | 0 | Don't overwrite user-defined coordinates attributes | tovogt 57705593 | - [x] Closes #6310 - [x] Tests added - [x] Doesn't include user visible changes or notable bug fixes for `whats-new.rst` - [x] No new functions/methods for `api.rst` As discussed in #6310, when setting "coordinates" as a variable attribute instead of as an encoding, the value of that variable attribute is overwritten when writing to a NetCDF file. This PR fixes it. | 2022-03-16T12:55:22Z | 2022-04-10T14:45:39Z | 2022-04-10T14:45:38Z | 2022-04-10T14:45:38Z | 2c68a8b851581773733ab75dfd36590b528635e3 | 0 | 8efe296f6391fe30d39215689150bd5558697c3c | 95bb9ae4233c16639682a532c14b26a3ea2728f3 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6366 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);