pull_requests
2 rows where user = 28786187
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 683909980 | MDExOlB1bGxSZXF1ZXN0NjgzOTA5OTgw | 5580 | closed | 0 | dataset `__repr__` updates | st-bender 28786187 | <!-- Feel free to remove check-list items aren't relevant to your change --> After discussing the recent change in the dataset `__repr__`, this implements the compromise discussed in #5545. It keeps the dataset `__repr__` short, tunable via `xr.set_options()`, and gives the full output via `ds.coords`, `ds.data_vars`, and `ds.attrs`. Passes the (updated) testsuite (locally). - [x] Closes #5545 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` | 2021-07-05T20:03:55Z | 2021-08-21T22:51:16Z | 2021-08-21T22:51:03Z | 2021-08-21T22:51:02Z | a78c1e0115d38cb4461fd1aba93334d440cff49c | 0 | 71cf034820f98096856156be71bed8d35a037be8 | 4bb9d9c6df77137f05e85c7cc6508fe7a93dc0e4 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5580 | ||||
| 1816204448 | PR_kwDOAMm_X85sQRSg | 8924 | open | 0 | Keep attributes for "bounds" variables | st-bender 28786187 | Issue #2921 is about mismatching time units between a time variable and its "bounds" companion. However, #2965 does more than fixing #2921, it removes all double attributes from "bounds" variables which has the undesired side effect that there is currently no way to save them to netcdf with xarray. Since the mentioned link is a recommendation and not a hard requirement for CF compliance, these attributes should be left to the caller to prepare the dataset variables appropriately if required. Reduces the amount of surprise that attributes are not written to disk and fixes #8368. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #8368 - [ ] Tests added (simple round trip test would be in issue #8368) - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` (not sure about "user visibility" here) | 2024-04-10T14:29:58Z | 2024-04-11T14:09:48Z | 7bfc111e9786c7aede6169c44fe2531a7f16ed9c | 0 | e8aa5c5235803ee7992b9486137ac548723f1af1 | 07c7f969fe879af7a871374209957d5cd1ddb5aa | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/8924 |
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]);