issue_comments
2 rows where author_association = "MEMBER", issue = 606530049 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- [community] Bi-weekly community developers meeting · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1530685353 | https://github.com/pydata/xarray/issues/4001#issuecomment-1530685353 | https://api.github.com/repos/pydata/xarray/issues/4001 | IC_kwDOAMm_X85bPGep | shoyer 1217238 | 2023-05-02T00:35:52Z | 2023-05-02T00:35:52Z | MEMBER | Can we delete the "Flexible indexes" meeting? It doesn't happen anymore. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
[community] Bi-weekly community developers meeting 606530049 | |
718076712 | https://github.com/pydata/xarray/issues/4001#issuecomment-718076712 | https://api.github.com/repos/pydata/xarray/issues/4001 | MDEyOklzc3VlQ29tbWVudDcxODA3NjcxMg== | shoyer 1217238 | 2020-10-28T17:05:07Z | 2020-10-28T17:05:07Z | MEMBER | Next week I think Europe and the US will be back in sync with daylight saving time. So both the PT and CET times will be good again? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
[community] Bi-weekly community developers meeting 606530049 |
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