issue_comments
2 rows where issue = 28123550 and user = 1794715 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Version now contains git commit ID · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 35839091 | https://github.com/pydata/xarray/pull/15#issuecomment-35839091 | https://api.github.com/repos/pydata/xarray/issues/15 | MDEyOklzc3VlQ29tbWVudDM1ODM5MDkx | ebrevdo 1794715 | 2014-02-23T18:43:08Z | 2014-02-23T18:43:08Z | CONTRIBUTOR | Fair enough. On Sun, Feb 23, 2014 at 10:40 AM, Stephan Hoyer notifications@github.comwrote:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Version now contains git commit ID 28123550 | |
| 35838795 | https://github.com/pydata/xarray/pull/15#issuecomment-35838795 | https://api.github.com/repos/pydata/xarray/issues/15 | MDEyOklzc3VlQ29tbWVudDM1ODM4Nzk1 | ebrevdo 1794715 | 2014-02-23T18:32:44Z | 2014-02-23T18:32:44Z | CONTRIBUTOR | Hmm. Would it be cleaner to use the git-python library? It would be cleaner than running a subprocess with possibly unknown versions of git. In addition, you could have it a requirement only for the build, not for installation. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Version now contains git commit ID 28123550 |
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