issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 741115905 and user = 13301940 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

  • andersy005 · 1 ✖

issue 1

  • nightly upstream test · 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
726234456 https://github.com/pydata/xarray/issues/4574#issuecomment-726234456 https://api.github.com/repos/pydata/xarray/issues/4574 MDEyOklzc3VlQ29tbWVudDcyNjIzNDQ1Ng== andersy005 13301940 2020-11-12T17:47:19Z 2020-11-12T17:47:29Z MEMBER

Thank you for the ping, @jhamman!

In a very ideal world, a failed nightly build would open an issue (or comment on an existing one) rather than send an email.

I concur with you Joe. I think this is 💯 doable today. I'm going to work on pushing it forward today, and will submit a PR once it's ready. 

{
    "total_count": 4,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 4,
    "rocket": 0,
    "eyes": 0
}
   nightly upstream test 741115905

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