issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 466004569 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • shoyer · 1 ✖

issue 1

  • WIP: more annotations · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
510323490 https://github.com/pydata/xarray/pull/3090#issuecomment-510323490 https://api.github.com/repos/pydata/xarray/issues/3090 MDEyOklzc3VlQ29tbWVudDUxMDMyMzQ5MA== shoyer 1217238 2019-07-11T04:23:06Z 2019-07-11T04:23:06Z MEMBER

Thanks @crusaderky. This is great, please keep them coming!

By the way, codecov updates its coverage reports as the tests on Azure complete. So usually in the first comment you'll see absurdly low coverage, but if you wait another ten minutes it will edit with the complete results. I don't know how to fix this easily, but fortunately it's only a minor annoyance.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   WIP: more annotations 466004569

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