issue_comments
1 row where issue = 760574919 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- increase the visibility of the upstream-dev PR CI · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
742047513 | https://github.com/pydata/xarray/issues/4670#issuecomment-742047513 | https://api.github.com/repos/pydata/xarray/issues/4670 | MDEyOklzc3VlQ29tbWVudDc0MjA0NzUxMw== | shoyer 1217238 | 2020-12-09T21:01:27Z | 2020-12-09T21:01:27Z | MEMBER |
I agree, I think is probably an acceptable compromise. Most bugs with upstream-dev occur with existing code in xarray, not new code introduced by a PR. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
increase the visibility of the upstream-dev PR CI 760574919 |
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