issue_comments
2 rows where issue = 396285440 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- dataset info in .json format · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
462912011 | https://github.com/pydata/xarray/issues/2656#issuecomment-462912011 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ2MjkxMjAxMQ== | jhamman 2443309 | 2019-02-12T20:01:07Z | 2019-02-12T20:01:07Z | MEMBER | It would be good to figure out if either of these are used. It's not too late to update your implementation. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
451777071 | https://github.com/pydata/xarray/issues/2656#issuecomment-451777071 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ1MTc3NzA3MQ== | jhamman 2443309 | 2019-01-06T21:35:50Z | 2019-01-06T21:35:50Z | MEMBER | Just to say, I really like this idea. I think I prefer the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 |
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