issue_comments
2 rows where issue = 393710539 and user = 6815844 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Is pep8speaks working well? · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 450553450 | https://github.com/pydata/xarray/issues/2627#issuecomment-450553450 | https://api.github.com/repos/pydata/xarray/issues/2627 | MDEyOklzc3VlQ29tbWVudDQ1MDU1MzQ1MA== | fujiisoup 6815844 | 2018-12-30T11:08:41Z | 2018-12-30T11:08:41Z | MEMBER | Closed via #2632 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Is pep8speaks working well? 393710539 | |
| 449619351 | https://github.com/pydata/xarray/issues/2627#issuecomment-449619351 | https://api.github.com/repos/pydata/xarray/issues/2627 | MDEyOklzc3VlQ29tbWVudDQ0OTYxOTM1MQ== | fujiisoup 6815844 | 2018-12-23T07:23:10Z | 2018-12-23T07:23:10Z | MEMBER | @max-sixty Pep8speaks edits his first comment for every push (he looks testing) probably to avoid adding too many comments to the thread. But it is now easy to review the pep8 violation if the thread becomes large. Personally, I feel it is not the best solution for the smooth development. If you have an alternative in your mind and could set it up, it'll be super nice. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Is pep8speaks working well? 393710539 |
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