issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 655382009 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • max-sixty · 3 ✖

issue 1

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

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1100945568 https://github.com/pydata/xarray/issues/4218#issuecomment-1100945568 https://api.github.com/repos/pydata/xarray/issues/4218 IC_kwDOAMm_X85Bnxig max-sixty 5635139 2022-04-17T20:34:32Z 2022-04-17T20:34:32Z 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

I think that's the right approach, so closing. Feel free to reopen though

 
{
    "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
657258662 https://github.com/pydata/xarray/issues/4218#issuecomment-657258662 https://api.github.com/repos/pydata/xarray/issues/4218 MDEyOklzc3VlQ29tbWVudDY1NzI1ODY2Mg== max-sixty 5635139 2020-07-12T18:30:40Z 2020-07-12T18:30:40Z MEMBER

It looks like @keewis isn't in https://github.com/orgs/pydata/teams/xarray/members so he couldn't change the permissions, can we change that? I think only @shoyer can add people to that team.

Me and @jhamman seem to be in both that team and added to https://github.com/pydata/xarray/settings/access, which seems redundant (though not causing any bad outcomes either)

 
{
    "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
657258596 https://github.com/pydata/xarray/issues/4218#issuecomment-657258596 https://api.github.com/repos/pydata/xarray/issues/4218 MDEyOklzc3VlQ29tbWVudDY1NzI1ODU5Ng== max-sixty 5635139 2020-07-12T18:30:07Z 2020-07-12T18:30:07Z MEMBER

No stress @fujiisoup ! Glad this worked out.

We could disable push access and then people can manually re-enable when necessary. But no strong view.

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