issue_comments

Table actions

2 rows where issue = 682040124 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

These facets timed out: author_association

user 1

  • max-sixty · 2 ✖

issue 1

  • update the instructions in the contributing guide · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
676746088 https://github.com/pydata/xarray/pull/4355#issuecomment-676746088 https://api.github.com/repos/pydata/xarray/issues/4355 MDEyOklzc3VlQ29tbWVudDY3Njc0NjA4OA== max-sixty 5635139 2020-08-19T22:03:05Z 2020-08-19T22:03:05Z MEMBER

re contributing docs: would it be best to leave that to the planned docs overhaul?

For sure, I didn't mean to weigh down this PR

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   update the instructions in the contributing guide 682040124
676708744 https://github.com/pydata/xarray/pull/4355#issuecomment-676708744 https://api.github.com/repos/pydata/xarray/issues/4355 MDEyOklzc3VlQ29tbWVudDY3NjcwODc0NA== max-sixty 5635139 2020-08-19T21:15:47Z 2020-08-19T21:15:47Z MEMBER

Agree with these changes, thanks @keewis

Stepping back on the contributing doc — I admit I haven't look at it in a while — I wonder whether we can slim it down a bit, for example by linking to other docs for generic tooling — I imagine we're unlikely to have the best docs on working with GH, for example. Or referencing our PR template rather than the (now out-of-date) PR checklist.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   update the instructions in the contributing guide 682040124

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