issue_comments
2 rows where author_association = "MEMBER", issue = 101719623 and user = 5356122 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Fix contour color · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
135587730 | https://github.com/pydata/xarray/pull/538#issuecomment-135587730 | https://api.github.com/repos/pydata/xarray/issues/538 | MDEyOklzc3VlQ29tbWVudDEzNTU4NzczMA== | clarkfitzg 5356122 | 2015-08-27T23:59:33Z | 2015-08-27T23:59:33Z | MEMBER | @rabernat We were all Git noobs at some point- don't worry about it! Seaborn should not be a dependency. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix contour color 101719623 | |
134281471 | https://github.com/pydata/xarray/pull/538#issuecomment-134281471 | https://api.github.com/repos/pydata/xarray/issues/538 | MDEyOklzc3VlQ29tbWVudDEzNDI4MTQ3MQ== | clarkfitzg 5356122 | 2015-08-24T16:19:57Z | 2015-08-24T16:19:57Z | MEMBER | @shoyer has laid out a nice plan. @rabernat do you feel like taking this on now? If not we can merge this and implement the rest later. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix contour color 101719623 |
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