issue_comments
1 row where issue = 1318800553 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- Require a pull request before merging to main · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1197129426 | https://github.com/pydata/xarray/issues/6833#issuecomment-1197129426 | https://api.github.com/repos/pydata/xarray/issues/6833 | IC_kwDOAMm_X85HWr7S | max-sixty 5635139 | 2022-07-27T18:15:00Z | 2022-07-27T18:15:00Z | MEMBER | If this is helpful to anyone, here are some configs I use to: a) avoid opening a browser b) avoid pushing to main This will push the current branch, and tell GH to merge as soon as test pass. I never feel the need to push to main now; even something like the release cleanup can be done through an PR.
(the latter can be replaced with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Require a pull request before merging to main 1318800553 |
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