issue_comments

Table actions

3 rows where issue = 423493491 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Small fix: use == to compare strings · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
475906336 https://github.com/pydata/xarray/pull/2832#issuecomment-475906336 https://api.github.com/repos/pydata/xarray/issues/2832 MDEyOklzc3VlQ29tbWVudDQ3NTkwNjMzNg== shoyer 1217238 2019-03-23T21:30:22Z 2019-03-23T21:30:22Z MEMBER

I think pep8speaks supports flake8 checks now, so that is a viable option. Previously it only did pycodestyle, and I didn't want to force people to read the build logs to get lint errors.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Small fix: use == to compare strings 423493491
475898628 https://github.com/pydata/xarray/pull/2832#issuecomment-475898628 https://api.github.com/repos/pydata/xarray/issues/2832 MDEyOklzc3VlQ29tbWVudDQ3NTg5ODYyOA== max-sixty 5635139 2019-03-23T19:40:56Z 2019-03-23T19:40:56Z MEMBER

I picked this and https://github.com/pydata/xarray/issues/2833 up b/c I have flake8 checking in my editor.

I think we moved to restricting our automated checks to pycodestyle https://github.com/pydata/xarray/pull/2642 rather than the fuller flake8. I'm generally keen on more automated checks and less reliance on humans, but defer to @shoyer as ever

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Small fix: use == to compare strings 423493491
475459416 https://github.com/pydata/xarray/pull/2832#issuecomment-475459416 https://api.github.com/repos/pydata/xarray/issues/2832 MDEyOklzc3VlQ29tbWVudDQ3NTQ1OTQxNg== shoyer 1217238 2019-03-22T01:12:59Z 2019-03-22T01:12:59Z MEMBER

thanks, this is definitely the right thing to do

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Small fix: use == to compare strings 423493491

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