issue_comments
1 row where author_association = "CONTRIBUTOR", issue = 205248365 and user = 6200806 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Clarifying sel/drop behavior for dims with vs. without coords · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
277558059 | https://github.com/pydata/xarray/issues/1248#issuecomment-277558059 | https://api.github.com/repos/pydata/xarray/issues/1248 | MDEyOklzc3VlQ29tbWVudDI3NzU1ODA1OQ== | spencerahill 6200806 | 2017-02-05T23:09:39Z | 2017-02-05T23:09:39Z | CONTRIBUTOR | Sorry this example wasn't clear.
Yes, this looks like the perfect solution for our use-case. My mistake for not reading the docs carefully enough. Thanks! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Clarifying sel/drop behavior for dims with vs. without coords 205248365 |
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