issue_comments
2 rows where issue = 767941842 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- deprecate open_rasterio in favour of a rioxarray entrypoint? · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
822647062 | https://github.com/pydata/xarray/issues/4697#issuecomment-822647062 | https://api.github.com/repos/pydata/xarray/issues/4697 | MDEyOklzc3VlQ29tbWVudDgyMjY0NzA2Mg== | max-sixty 5635139 | 2021-04-19T17:32:56Z | 2021-04-19T17:32:56Z | MEMBER | OK great @alexamici |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842 | |
822641695 | https://github.com/pydata/xarray/issues/4697#issuecomment-822641695 | https://api.github.com/repos/pydata/xarray/issues/4697 | MDEyOklzc3VlQ29tbWVudDgyMjY0MTY5NQ== | max-sixty 5635139 | 2021-04-19T17:23:59Z | 2021-04-19T17:23:59Z | MEMBER | I think we could release 0.17.1 fairly soon — nothing is pending but it's also fairly easy to do a release. Do we want to deprecate |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 1