issues: 466750687
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 466750687 | MDU6SXNzdWU0NjY3NTA2ODc= | 3092 | black formatting | 6213168 | closed | 0 | 14 | 2019-07-11T08:43:55Z | 2019-08-08T22:34:53Z | 2019-08-08T22:34:53Z | MEMBER | I, like many others, have irreversibly fallen in love with black. Can we apply it to the existing codebase and as an enforced CI test? The only (big) problem is that developers will need to manually apply it to any open branches and then merge from master - and even then, merging likely won't be trivial. How did the dask project tackle the issue? |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3092/reactions",
"total_count": 3,
"+1": 3,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |