issue_comments
2 rows where issue = 482023929 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Building the docs creates temporary files · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 525369517 | https://github.com/pydata/xarray/issues/3227#issuecomment-525369517 | https://api.github.com/repos/pydata/xarray/issues/3227 | MDEyOklzc3VlQ29tbWVudDUyNTM2OTUxNw== | max-sixty 5635139 | 2019-08-27T16:02:53Z | 2019-08-27T16:02:53Z | MEMBER | Great, thanks for the clear options @gwgundersen I don't have a strong view. I think either the Agree with @fmaussion re adding the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Building the docs creates temporary files 482023929 | |
| 522347626 | https://github.com/pydata/xarray/issues/3227#issuecomment-522347626 | https://api.github.com/repos/pydata/xarray/issues/3227 | MDEyOklzc3VlQ29tbWVudDUyMjM0NzYyNg== | max-sixty 5635139 | 2019-08-18T19:17:21Z | 2019-08-18T19:17:21Z | MEMBER | Yes, at the least we should add those to |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Building the docs creates temporary files 482023929 |
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