issue_comments

Table actions

2 rows where issue = 628436420 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • dcherian · 2 ✖

issue 1

  • xarray ufuncs · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
648874567 https://github.com/pydata/xarray/issues/4116#issuecomment-648874567 https://api.github.com/repos/pydata/xarray/issues/4116 MDEyOklzc3VlQ29tbWVudDY0ODg3NDU2Nw== dcherian 2448579 2020-06-24T14:59:35Z 2020-06-24T14:59:35Z MEMBER

I think we should put that warning (removed after support for 1.17 is dropped) into the documentation, too.

:+1:

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420
636862823 https://github.com/pydata/xarray/issues/4116#issuecomment-636862823 https://api.github.com/repos/pydata/xarray/issues/4116 MDEyOklzc3VlQ29tbWVudDYzNjg2MjgyMw== dcherian 2448579 2020-06-01T13:31:56Z 2020-06-01T13:31:56Z MEMBER

Sounds good to me

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420

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