pull_requests: 298998116
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
298998116 | MDExOlB1bGxSZXF1ZXN0Mjk4OTk4MTE2 | 3142 | closed | 0 | Black | 5635139 | From https://github.com/pydata/xarray/issues/3092 - [x] Reformat code - [x] CI checks - [x] Short instructions for how to merge an existing PR (i.e. avoid manual merge resolution) - Not sure if there's magic here - I think people would just have to format their code and then hope git can resolve (i.e. because there would still be no common parent)? - [x] Black badge - [x] Do we want to keep `flake8` checks? Black is mostly stricter but not always, e.g. on lines at the end of files. (+0.3 from me to use only `black` and stop using `flake8`) ~- [ ] Do we want to include `isort`? (-0.1 from me, even though I like the tool)~ | 2019-07-18T16:35:05Z | 2019-08-08T20:55:14Z | 2019-08-08T20:54:34Z | 2019-08-08T20:54:34Z | d089df385e737f71067309ff7abae15994d581ec | 0 | 6ec30779a7ade1dcdc230f208c1d04026dfd79b1 | f172c6738ae4bc9802e08d355ea05ea6c47527ab | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/3142 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests