issue_comments

Table actions

1 row where author_association = "CONTRIBUTOR" and user = 26591824 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

  • paigem · 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
1382401753 https://github.com/pydata/xarray/issues/7439#issuecomment-1382401753 https://api.github.com/repos/pydata/xarray/issues/7439 IC_kwDOAMm_X85SZcbZ paigem 26591824 2023-01-13T21:18:31Z 2023-01-13T21:18:31Z CONTRIBUTOR

One more comment (now that my docstring PR went through): - We should include something like the following under the section Finally, make the pull request : - "If you have made updates to the documentation, you can see a preview of the updated docs by clicking on "Details" under the docs/readthedocs.org check near the bottom of the list of checks that run automatically when submitting a PR."

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add clarifying language to contributor's guide 1532853152

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