issue_comments
2 rows where author_association = "MEMBER", issue = 806436724 and user = 5821660 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- release 0.17.0 · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
780735665 | https://github.com/pydata/xarray/issues/4894#issuecomment-780735665 | https://api.github.com/repos/pydata/xarray/issues/4894 | MDEyOklzc3VlQ29tbWVudDc4MDczNTY2NQ== | kmuehlbauer 5821660 | 2021-02-17T17:53:29Z | 2021-02-17T17:53:29Z | MEMBER |
No worries, @alexamici, as the API can be switched to v2 already, this is no major problem. Better safe than sorry wrt testing. Thank you and your colleagues! |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release 0.17.0 806436724 | |
780699009 | https://github.com/pydata/xarray/issues/4894#issuecomment-780699009 | https://api.github.com/repos/pydata/xarray/issues/4894 | MDEyOklzc3VlQ29tbWVudDc4MDY5OTAwOQ== | kmuehlbauer 5821660 | 2021-02-17T16:57:37Z | 2021-02-17T16:57:57Z | MEMBER |
This would be really great. But if it doesn't fit now, I hope a release will be cut right after finalising backend refactor. This is an eagerly awaited addition. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release 0.17.0 806436724 |
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