issue_comments
2 rows where issue = 526273373 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
These facets timed out: issue
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 557309786 | https://github.com/pydata/xarray/pull/3557#issuecomment-557309786 | https://api.github.com/repos/pydata/xarray/issues/3557 | MDEyOklzc3VlQ29tbWVudDU1NzMwOTc4Ng== | max-sixty 5635139 | 2019-11-21T22:56:31Z | 2019-11-21T22:56:31Z | MEMBER | Should we change the base of this PR to master? Then we can choose when we push to stable? (But let's not get stuck on this, fine to just go ahead if we can't resolve) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
merge scipy19 docs 526273373 | |
| 557308675 | https://github.com/pydata/xarray/pull/3557#issuecomment-557308675 | https://api.github.com/repos/pydata/xarray/issues/3557 | MDEyOklzc3VlQ29tbWVudDU1NzMwODY3NQ== | max-sixty 5635139 | 2019-11-21T22:53:09Z | 2019-11-21T22:53:09Z | MEMBER | Feel free to ignore since it's not a big deal relative to the benefits, but looks like this adds some recent changes on |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
merge scipy19 docs 526273373 |
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