pull_requests: 305772178
This data as json
id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
305772178 | MDExOlB1bGxSZXF1ZXN0MzA1NzcyMTc4 | 3195 | closed | 0 | Update black instructions | 5635139 | This needed updating with the relevant commit post-black change I also added a line to apply the patch of manual changes we made on top of the black changes. It makes the list of steps a bit burdensome. But I've tested them a couple of times and, where people have lots of code changes, it's still going to be much easier than resolving manually. I generally wouldn't want to suggest people curl data from the internet (even if we trust the individual). I think it's probably OK in this instance: the address contains a hash of the contents, and it's only being fed into `git apply -`, not executed. But lmk if that's still a security concern. I'll update the issue I opened on `black` with the above issue; we should have done one commit with only the `black` changes, and then another with any manual changes. | 2019-08-08T22:28:59Z | 2019-08-09T00:27:28Z | 2019-08-09T00:27:09Z | 2019-08-09T00:27:09Z | 5b36e80b5a5e790e1c533cae4382234c18bb37a1 | 0 | ce89ec20bbc37d27e5e90f2723c1647fe17a34fd | d089df385e737f71067309ff7abae15994d581ec | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/3195 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests