issue_comments

Table actions

5 rows where author_association = "MEMBER" and issue = 1045038245 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 1

  • Refresh on issue bots · 5 ✖

author_association 1

  • MEMBER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
964539712 https://github.com/pydata/xarray/issues/5940#issuecomment-964539712 https://api.github.com/repos/pydata/xarray/issues/5940 IC_kwDOAMm_X845fbVA andersy005 13301940 2021-11-09T21:01:31Z 2021-11-09T21:01:31Z MEMBER

In any case, I'd vote to remove the pre-commit autoupdate CI as that has some quirks that make it difficult to use for everyone other than me.

Once we're satisfied with pre-commit.ci, we should remove https://github.com/pydata/xarray/blob/main/.github/workflows/ci-pre-commit.yml workflow as well. 

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Refresh on issue bots 1045038245
962381375 https://github.com/pydata/xarray/issues/5940#issuecomment-962381375 https://api.github.com/repos/pydata/xarray/issues/5940 IC_kwDOAMm_X845XMY_ max-sixty 5635139 2021-11-06T03:05:02Z 2021-11-06T03:05:02Z MEMBER

Thanks for the thoughts. I enabled pre-commit.ci so we can see how that goes and remove the others if it's successful.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Refresh on issue bots 1045038245
961767895 https://github.com/pydata/xarray/issues/5940#issuecomment-961767895 https://api.github.com/repos/pydata/xarray/issues/5940 IC_kwDOAMm_X845U2nX keewis 14808389 2021-11-05T10:05:36Z 2021-11-05T10:05:36Z MEMBER

the only issues I have with pre-commit.ci is that it autofixes PRs so I have to remember to pull before adding new changes (but I think I can live with that, and the advantage is that lots of new contributors don't have to fight with our CI).

In any case, I'd vote to remove the pre-commit autoupdate CI as that has some quirks that make it difficult to use for everyone other than me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Refresh on issue bots 1045038245
961351543 https://github.com/pydata/xarray/issues/5940#issuecomment-961351543 https://api.github.com/repos/pydata/xarray/issues/5940 IC_kwDOAMm_X845TQ93 Illviljan 14371165 2021-11-04T19:28:06Z 2021-11-04T19:28:06Z MEMBER

I like pep8speaks because it's faster than the current linting CI. But if we start using the autofixer than that would make pep8speaks redundant.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Refresh on issue bots 1045038245
961336809 https://github.com/pydata/xarray/issues/5940#issuecomment-961336809 https://api.github.com/repos/pydata/xarray/issues/5940 IC_kwDOAMm_X845TNXp TomNicholas 35968931 2021-11-04T19:06:52Z 2021-11-04T19:06:52Z MEMBER

I agree with all 3 suggestions

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Refresh on issue bots 1045038245

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