issue_comments

Table actions

1 row where author_association = "CONTRIBUTOR" and issue = 1155634014 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 1

  • fix typos (using codespell) · 1 ✖

author_association 1

  • CONTRIBUTOR · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1187441055 https://github.com/pydata/xarray/pull/6316#issuecomment-1187441055 https://api.github.com/repos/pydata/xarray/issues/6316 IC_kwDOAMm_X85Gxumf DimitriPapadopoulos 3234522 2022-07-18T13:32:47Z 2022-07-18T13:33:02Z CONTRIBUTOR

Spell checking cannot be fully automated (yet?), you will always get false positives, especially in source code. For that reason, instead of adding it to hooks, it is probably better to share a common tool configuration, in file .codespellrc or setup.cfg, and let interested users fix typos from time to time.

I can add the proper configuration in setup.cfg if you agree.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   fix typos (using codespell) 1155634014

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