issue_comments

Table actions

where issue = 269886091 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
342578205 https://github.com/pydata/xarray/pull/1674#issuecomment-342578205 https://api.github.com/repos/pydata/xarray/issues/1674 MDEyOklzc3VlQ29tbWVudDM0MjU3ODIwNQ== shoyer 1217238 2017-11-07T18:33:09Z 2017-11-07T18:33:09Z MEMBER

Thanks Matt. I was just waiting for CI to pass.

I've indicated that this is experimental in the release notes, so as long as we keep the messaging consistent on the Dask side I think we have room to change this up if needed.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Support Dask interface 269886091

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);