issue_comments

Table actions

1 row where issue = 212501628 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

  • git version label yields version in violation of PEP 440 · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
284915996 https://github.com/pydata/xarray/issues/1300#issuecomment-284915996 https://api.github.com/repos/pydata/xarray/issues/1300 MDEyOklzc3VlQ29tbWVudDI4NDkxNTk5Ng== shoyer 1217238 2017-03-08T01:21:58Z 2017-03-08T01:21:58Z MEMBER

Yes, we should update this. Our current logic for determining git versions is in setup.py and was originally copied from pndnas, but we really should consider updating to use what dask and pandas now use, which is versioneer.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   git version label yields version in violation of PEP 440 212501628

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