issue_comments

Table actions

2 rows where issue = 233708091 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 · 2 ✖

issue 1

  • v0.9.6 release · 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
307439786 https://github.com/pydata/xarray/issues/1441#issuecomment-307439786 https://api.github.com/repos/pydata/xarray/issues/1441 MDEyOklzc3VlQ29tbWVudDMwNzQzOTc4Ng== shoyer 1217238 2017-06-09T16:43:59Z 2017-06-09T16:43:59Z MEMBER

So far, I've been saving major version numbers for breaking changes. But they are also useful to signal large advances in functionality, even if they don't break compatibility.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   v0.9.6 release 233708091
307428359 https://github.com/pydata/xarray/issues/1441#issuecomment-307428359 https://api.github.com/repos/pydata/xarray/issues/1441 MDEyOklzc3VlQ29tbWVudDMwNzQyODM1OQ== shoyer 1217238 2017-06-09T15:57:09Z 2017-06-09T15:57:09Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   v0.9.6 release 233708091

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