issue_comments
2 rows where issue = 192083180 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Unpin python on RTD · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
263411488 | https://github.com/pydata/xarray/pull/1139#issuecomment-263411488 | https://api.github.com/repos/pydata/xarray/issues/1139 | MDEyOklzc3VlQ29tbWVudDI2MzQxMTQ4OA== | fmaussion 10050469 | 2016-11-28T22:13:58Z | 2016-11-28T22:13:58Z | MEMBER |
I did, but my local builds still complete (with many warning but now errors: execfile seems to be simply ignored...). I'll remove the execfile, but I'm still skeptical that this will work (py3 support is relatively recent in py3) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unpin python on RTD 192083180 | |
263377404 | https://github.com/pydata/xarray/pull/1139#issuecomment-263377404 | https://api.github.com/repos/pydata/xarray/issues/1139 | MDEyOklzc3VlQ29tbWVudDI2MzM3NzQwNA== | shoyer 1217238 | 2016-11-28T20:00:11Z | 2016-11-28T20:00:11Z | MEMBER | Indeed, I think For debugging the doc build on Python 3, I would definitely recommend building locally (i.e., with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unpin python on RTD 192083180 |
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 2