home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where author_association = "MEMBER", issue = 655382009 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 2 ✖

issue 1

  • what is the best way to reset an unintentional direct push to the master · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
657261588 https://github.com/pydata/xarray/issues/4218#issuecomment-657261588 https://api.github.com/repos/pydata/xarray/issues/4218 MDEyOklzc3VlQ29tbWVudDY1NzI2MTU4OA== shoyer 1217238 2020-07-12T18:59:08Z 2020-07-12T18:59:08Z MEMBER

But anyways, this is not a big deal at all! Git makes it very easy to mess things up, but as long as we keep the master branch protected, it's always possible always possible to move forward by reverting changes -- there is no way to lose work.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  what is the best way to reset an unintentional direct push to the master 655382009
657261331 https://github.com/pydata/xarray/issues/4218#issuecomment-657261331 https://api.github.com/repos/pydata/xarray/issues/4218 MDEyOklzc3VlQ29tbWVudDY1NzI2MTMzMQ== shoyer 1217238 2020-07-12T18:56:53Z 2020-07-12T18:56:53Z MEMBER

As long as you don't force push (which is disabled), I think the preferred option for dealing with accidentally pushed changes is to push a "revert" commit generated from git revert

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  what is the best way to reset an unintentional direct push to the master 655382009

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]);
Powered by Datasette · Queries took 5122.684ms · About: xarray-datasette