issue_comments
2 rows where author_association = "MEMBER", issue = 484711431 and user = 6213168 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- 0.13.0 release · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
526548099 | https://github.com/pydata/xarray/issues/3257#issuecomment-526548099 | https://api.github.com/repos/pydata/xarray/issues/3257 | MDEyOklzc3VlQ29tbWVudDUyNjU0ODA5OQ== | crusaderky 6213168 | 2019-08-30T10:17:25Z | 2019-08-30T10:17:25Z | MEMBER | Can't we have a nightly build of docker images with all the xarray depencencies?
Then the individual CI jobs would literally become something like
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
0.13.0 release 484711431 | |
525199512 | https://github.com/pydata/xarray/issues/3257#issuecomment-525199512 | https://api.github.com/repos/pydata/xarray/issues/3257 | MDEyOklzc3VlQ29tbWVudDUyNTE5OTUxMg== | crusaderky 6213168 | 2019-08-27T08:32:41Z | 2019-08-27T08:32:41Z | MEMBER | Given that's 1 hour of work about once a month... Unless there is appetite for increasing the release frequency, I would say automation is overkill |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
0.13.0 release 484711431 |
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