issue_comments

Table actions

where issue = 462122623 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 1 ✖

issue 1

  • Argument and its type joined in docs · 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
506803859 https://github.com/pydata/xarray/issues/3056#issuecomment-506803859 https://api.github.com/repos/pydata/xarray/issues/3056 MDEyOklzc3VlQ29tbWVudDUwNjgwMzg1OQ== shoyer 1217238 2019-06-28T16:53:23Z 2019-06-28T16:53:23Z MEMBER

I agree, this is definitely not ideal.

It's definitely an upstream issue with the theme we use for our docs -- possibly https://github.com/rtfd/sphinx_rtd_theme/issues/750?

It would be great if you (or anyone else) wants to look into this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Argument and its type joined in docs 462122623

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