issue_comments
2 rows where issue = 489270698 and user = 10194086 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Deprecation cycles to finish for xarray 0.13 · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
529523741 | https://github.com/pydata/xarray/issues/3280#issuecomment-529523741 | https://api.github.com/repos/pydata/xarray/issues/3280 | MDEyOklzc3VlQ29tbWVudDUyOTUyMzc0MQ== | mathause 10194086 | 2019-09-09T15:10:55Z | 2019-09-09T15:10:55Z | MEMBER | Yes, fine for me. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Deprecation cycles to finish for xarray 0.13 489270698 | |
528787208 | https://github.com/pydata/xarray/issues/3280#issuecomment-528787208 | https://api.github.com/repos/pydata/xarray/issues/3280 | MDEyOklzc3VlQ29tbWVudDUyODc4NzIwOA== | mathause 10194086 | 2019-09-06T09:39:51Z | 2019-09-06T09:39:51Z | MEMBER |
I am a bit worried about the 3rd last item on your list. I currently still rely on this behavior because the alternative does not work for me, see #3284. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Deprecation cycles to finish for xarray 0.13 489270698 |
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