home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 657273886

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/4218#issuecomment-657273886 https://api.github.com/repos/pydata/xarray/issues/4218 657273886 MDEyOklzc3VlQ29tbWVudDY1NzI3Mzg4Ng== 6815844 2020-07-12T20:55:53Z 2020-07-12T20:55:53Z MEMBER

I think the preferred option for dealing with accidentally pushed changes is to push a "revert" commit generated from git revert

OK, understood.

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.

Then, probably the most dangarous part was when I unprotected the master branch. I was afraid of messing up the commit history, but it is much better than losing entire commit history...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  655382009
Powered by Datasette · Queries took 0.902ms · About: xarray-datasette