issue_comments

Table actions

1 row where issue = 94508580 and user = 2443309 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

  • jhamman · 1 ✖

issue 1

  • Option for closing files with scipy backend · 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
129285729 https://github.com/pydata/xarray/pull/468#issuecomment-129285729 https://api.github.com/repos/pydata/xarray/issues/468 MDEyOklzc3VlQ29tbWVudDEyOTI4NTcyOQ== jhamman 2443309 2015-08-10T03:00:50Z 2015-08-10T03:00:50Z MEMBER

Ah, yes. Open a new PR. You must have pushed your rebased master to your fork.

In general, I never edit on my fork's master branch. My typical workflow is to create separate feature branches off the xray/xray:master branch:

``` bash git checkout master git pull upstream master git checkout -b feature/my_feature

...edit...

git add edited_files* git commit ... git push origin feature/my_feature

create pull request from my fork's feature/my_feature to xray:master on github

```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Option for closing files with scipy backend 94508580

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