issue_comments

Table actions

1 row where issue = 1562408536 and user = 3129530 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

  • mwestphal · 1 ✖

issue 1

  • Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible · 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
1412411490 https://github.com/pydata/xarray/issues/7486#issuecomment-1412411490 https://api.github.com/repos/pydata/xarray/issues/7486 IC_kwDOAMm_X85UL7Bi mwestphal 3129530 2023-02-01T17:08:31Z 2023-02-01T17:08:31Z NONE

or the entire section (personally, I would lean towards the latter).

That was definitely not my goal, as I was about to publish a blog linking to that very section as an example. Of course, i'm merely a user here.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible 1562408536

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