issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 296867544 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • jhamman · 3 ✖

issue 1

  • Build documentation on TravisCI · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
366021245 https://github.com/pydata/xarray/pull/1908#issuecomment-366021245 https://api.github.com/repos/pydata/xarray/issues/1908 MDEyOklzc3VlQ29tbWVudDM2NjAyMTI0NQ== jhamman 2443309 2018-02-15T18:38:58Z 2018-02-15T18:38:58Z MEMBER

I had the fail-on-warning option turned on. I agree we should drop that for now. After we merge this, I'll open an issue to track cleaning those up at some point. I don't have time to fix them right now. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Build documentation on TravisCI 296867544
365407044 https://github.com/pydata/xarray/pull/1908#issuecomment-365407044 https://api.github.com/repos/pydata/xarray/issues/1908 MDEyOklzc3VlQ29tbWVudDM2NTQwNzA0NA== jhamman 2443309 2018-02-13T21:17:06Z 2018-02-13T21:17:06Z MEMBER

Well isn't that nice. CI is a two edged sword! I'll take a look.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Build documentation on TravisCI 296867544
365387791 https://github.com/pydata/xarray/pull/1908#issuecomment-365387791 https://api.github.com/repos/pydata/xarray/issues/1908 MDEyOklzc3VlQ29tbWVudDM2NTM4Nzc5MQ== jhamman 2443309 2018-02-13T20:06:42Z 2018-02-13T20:06:42Z MEMBER

I think we've talked about doing this a number of times in the past. It seems that we've been running into a number of uncaught build failures (e.g. #1898, #1881). This is one way of testing that the documentation build will pass on read the docs. If someone has a better of idea of how to do this, I'm all ears.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Build documentation on TravisCI 296867544

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