issue_comments
2 rows where issue = 307783090 and user = 223250 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- rolling: allow control over padding · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
880141480 | https://github.com/pydata/xarray/issues/2007#issuecomment-880141480 | https://api.github.com/repos/pydata/xarray/issues/2007 | MDEyOklzc3VlQ29tbWVudDg4MDE0MTQ4MA== | kmsquire 223250 | 2021-07-14T19:10:46Z | 2021-07-14T19:10:46Z | CONTRIBUTOR | I added support for That fixes, e.g., #4743, but I don't think it's a complete fix for this issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
rolling: allow control over padding 307783090 | |
876103462 | https://github.com/pydata/xarray/issues/2007#issuecomment-876103462 | https://api.github.com/repos/pydata/xarray/issues/2007 | MDEyOklzc3VlQ29tbWVudDg3NjEwMzQ2Mg== | kmsquire 223250 | 2021-07-08T03:55:33Z | 2021-07-08T03:55:33Z | CONTRIBUTOR |
For this API, it seems that the only thing that would need to be implemented would be adding a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
rolling: allow control over padding 307783090 |
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