issue_comments
2 rows where issue = 189095110 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- Do not convert subclasses of `ndarray` unless required · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
568903769 | https://github.com/pydata/xarray/pull/1118#issuecomment-568903769 | https://api.github.com/repos/pydata/xarray/issues/1118 | MDEyOklzc3VlQ29tbWVudDU2ODkwMzc2OQ== | keewis 14808389 | 2019-12-25T14:12:33Z | 2019-12-25T14:12:33Z | MEMBER | closing for the same reason as #2956 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Do not convert subclasses of `ndarray` unless required 189095110 | |
491620350 | https://github.com/pydata/xarray/pull/1118#issuecomment-491620350 | https://api.github.com/repos/pydata/xarray/issues/1118 | MDEyOklzc3VlQ29tbWVudDQ5MTYyMDM1MA== | keewis 14808389 | 2019-05-12T19:01:19Z | 2019-05-12T19:01:19Z | MEMBER | Is this still relevant? If so, I'd be willing to take over. However, I am not really familiar with github yet: would I open a new pull request for that? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Do not convert subclasses of `ndarray` unless required 189095110 |
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