issue_comments
1 row where issue = 382497709 and user = 703554 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Zarr consolidated · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
442801741 | https://github.com/pydata/xarray/pull/2559#issuecomment-442801741 | https://api.github.com/repos/pydata/xarray/issues/2559 | MDEyOklzc3VlQ29tbWVudDQ0MjgwMTc0MQ== | alimanfoo 703554 | 2018-11-29T11:33:33Z | 2018-11-29T11:33:33Z | CONTRIBUTOR | Great to see this. On the API, FWIW I'd vote for using the same keyword ( |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Zarr consolidated 382497709 |
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