issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 625064501 and user = 14808389 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

  • keewis · 1 ✖

issue 1

  • Corrcov typo fix · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
634216856 https://github.com/pydata/xarray/pull/4096#issuecomment-634216856 https://api.github.com/repos/pydata/xarray/issues/4096 MDEyOklzc3VlQ29tbWVudDYzNDIxNjg1Ng== keewis 14808389 2020-05-26T19:03:15Z 2020-05-26T19:03:15Z MEMBER

thanks, @AndrewWilliams3142.

About git / github: I think the most common workflow is that you have a local branch (commonly named master, but could be anything) that tracks origin/master and a lot of features branches you use to open PRs. If you think there are changes to master you need in your branch (or because Github complains about merge conflicts), you can use sh git checkout master git pull origin master # could also be `git pull` or `git pull origin` git checkout <feature-branch> git merge master

 
{
    "total_count": 2,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 1,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Corrcov typo fix 625064501

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