issue_comments
2 rows where issue = 777588292 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Write black diff on errors · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 753675027 | https://github.com/pydata/xarray/pull/4754#issuecomment-753675027 | https://api.github.com/repos/pydata/xarray/issues/4754 | MDEyOklzc3VlQ29tbWVudDc1MzY3NTAyNw== | max-sixty 5635139 | 2021-01-03T20:57:13Z | 2021-01-03T20:57:13Z | MEMBER | Oh nice, I hadn't seen that. That's much better. I'll merge this regardless but we can remove along with the rest of Azure when that merges — hopefully this will have a limited lifespan 😄 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Write black diff on errors 777588292 | |
| 753674569 | https://github.com/pydata/xarray/pull/4754#issuecomment-753674569 | https://api.github.com/repos/pydata/xarray/issues/4754 | MDEyOklzc3VlQ29tbWVudDc1MzY3NDU2OQ== | keewis 14808389 | 2021-01-03T20:52:55Z | 2021-01-03T20:52:55Z | MEMBER | I would do that for Be aware that #4730 replaces the current style check CI with a |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Write black diff on errors 777588292 |
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 2