issue_comments

Table actions

3 rows where issue = 158902764 and user = 10050469 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

  • fmaussion · 3 ✖

issue 1

  • ENH: more control on colorbar · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
224933442 https://github.com/pydata/xarray/pull/872#issuecomment-224933442 https://api.github.com/repos/pydata/xarray/issues/872 MDEyOklzc3VlQ29tbWVudDIyNDkzMzQ0Mg== fmaussion 10050469 2016-06-09T15:33:31Z 2016-06-09T15:33:46Z MEMBER

Yes, ok.

[OT]: Some people on the mpl mailing list said it was a dangerous feature of github but I didn't understand why. I guess that for large PRs it might be useful to keep the intermediate commits, but for the majority of the cases it makes the git history much clearer I think.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: more control on colorbar 158902764
224931210 https://github.com/pydata/xarray/pull/872#issuecomment-224931210 https://api.github.com/repos/pydata/xarray/issues/872 MDEyOklzc3VlQ29tbWVudDIyNDkzMTIxMA== fmaussion 10050469 2016-06-09T15:26:22Z 2016-06-09T15:26:22Z MEMBER

Right, I always forget about this one. Let me know if I should rebase, too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: more control on colorbar 158902764
224845352 https://github.com/pydata/xarray/pull/872#issuecomment-224845352 https://api.github.com/repos/pydata/xarray/issues/872 MDEyOklzc3VlQ29tbWVudDIyNDg0NTM1Mg== fmaussion 10050469 2016-06-09T09:31:40Z 2016-06-09T09:31:40Z MEMBER

@shoyer I added some tests and and implemented @jhamman 's comments. I am not a big fan of raising an error when keywords are set and not used, but I don't have a use case for this either so I implemented it as requested ;)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: more control on colorbar 158902764

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