issue_comments
2 rows where author_association = "MEMBER", issue = 1412019155 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Lazy Imports · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1282995923 | https://github.com/pydata/xarray/pull/7179#issuecomment-1282995923 | https://api.github.com/repos/pydata/xarray/issues/7179 | IC_kwDOAMm_X85MePbT | max-sixty 5635139 | 2022-10-18T20:58:04Z | 2022-10-18T20:58:04Z | MEMBER | Do you think there's a risk something gets added back by mistake? A galaxy brain idea is to have a lint in pre-commit which looks for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Lazy Imports 1412019155 | |
1281527397 | https://github.com/pydata/xarray/pull/7179#issuecomment-1281527397 | https://api.github.com/repos/pydata/xarray/issues/7179 | IC_kwDOAMm_X85MYo5l | max-sixty 5635139 | 2022-10-17T21:36:58Z | 2022-10-17T21:36:58Z | MEMBER | Very nice @headtr1ck ! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Lazy Imports 1412019155 |
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