issue_comments
2 rows where issue = 812214755 and user = 14808389 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
783502149 | https://github.com/pydata/xarray/pull/4929#issuecomment-783502149 | https://api.github.com/repos/pydata/xarray/issues/4929 | MDEyOklzc3VlQ29tbWVudDc4MzUwMjE0OQ== | keewis 14808389 | 2021-02-22T16:33:45Z | 2021-02-22T16:33:45Z | MEMBER | Thanks, @mathause, looks good to me. I wonder if we should move this into |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CI: run mypy in full env 812214755 | |
782239279 | https://github.com/pydata/xarray/pull/4929#issuecomment-782239279 | https://api.github.com/repos/pydata/xarray/issues/4929 | MDEyOklzc3VlQ29tbWVudDc4MjIzOTI3OQ== | keewis 14808389 | 2021-02-19T17:59:48Z | 2021-02-19T23:36:30Z | MEMBER | the workflow looks good to me, but it should probably be possible to skip it using Edit: since it will always fail right now, should we disable this workflow for now and you enable it in #4878? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
CI: run mypy in full env 812214755 |
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