issue_comments
2 rows where author_association = "MEMBER", issue = 490752037 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association, issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
529885673 | https://github.com/pydata/xarray/issues/3293#issuecomment-529885673 | https://api.github.com/repos/pydata/xarray/issues/3293 | MDEyOklzc3VlQ29tbWVudDUyOTg4NTY3Mw== | max-sixty 5635139 | 2019-09-10T11:06:06Z | 2019-09-10T11:06:06Z | MEMBER |
What are the semver rules for underlying versions? If we drop 3.5 support, do we need a minor version increase to 0.14, or is a patch release to 0.13.1 OK? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Drop 3.5 after 0.13? 490752037 | |
529885174 | https://github.com/pydata/xarray/issues/3293#issuecomment-529885174 | https://api.github.com/repos/pydata/xarray/issues/3293 | MDEyOklzc3VlQ29tbWVudDUyOTg4NTE3NA== | max-sixty 5635139 | 2019-09-10T11:04:27Z | 2019-09-10T11:04:27Z | MEMBER | I wasn't initially suggesting for 0.13 but not opposed to it What about releasing 0.13 and then dropping 3.5? That way any 3.5 users have an up-to-date version and we can have a master on 3.6 very soon |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Drop 3.5 after 0.13? 490752037 |
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