issue_comments
2 rows where issue = 870619014 and user = 226037 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Code cleanup · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 831856905 | https://github.com/pydata/xarray/pull/5234#issuecomment-831856905 | https://api.github.com/repos/pydata/xarray/issues/5234 | MDEyOklzc3VlQ29tbWVudDgzMTg1NjkwNQ== | alexamici 226037 | 2021-05-04T11:02:15Z | 2021-05-04T11:02:15Z | MEMBER | @max-sixty & @andersy005 mine was more of a general comment. It is OK to merge it for me, but please after the release! |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Code cleanup 870619014 | |
| 831740472 | https://github.com/pydata/xarray/pull/5234#issuecomment-831740472 | https://api.github.com/repos/pydata/xarray/issues/5234 | MDEyOklzc3VlQ29tbWVudDgzMTc0MDQ3Mg== | alexamici 226037 | 2021-05-04T07:32:32Z | 2021-05-04T07:32:32Z | MEMBER | I feel this PR is too big and diverse to accept it as a whole. For example I like most changes from older style formatting to f-strings, but I disagree strongly the moving the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Code cleanup 870619014 |
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