You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/contributing.rst
-15Lines changed: 0 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -381,21 +381,6 @@ and then running::
381
381
from the root of the xarray repository. You can skip the pre-commit checks with
382
382
``git commit --no-verify``.
383
383
384
-
.. note::
385
-
386
-
If you were working on a branch *prior* to the code being reformatted with black,
387
-
you will likely face some merge conflicts. These steps can eliminate many of those
388
-
conflicts. Because they have had limited testing, please reach out to the core devs
389
-
on your pull request if you face any issues, and we'll help with the merge:
390
-
391
-
- Merge the commit on master prior to the ``black`` commit into your branch
392
-
``git merge f172c673``. If you have conflicts here, resolve and commit.
393
-
- Apply ``black .`` to your branch and commit ``git commit -am "black"``
394
-
- Apply a patch of other changes we made on that commit: ``curl https://gist.githubusercontent.com/max-sixty/3cceb8472ed4ea806353999ca43aed52/raw/03cbee4e386156bddb61acaa250c0bfc726f596d/xarray%2520black%2520diff | git apply -``
395
-
- Commit (``git commit -am "black2"``)
396
-
- Merge master at the ``black`` commit, resolving in favor of 'our' changes:
397
-
``git merge d089df38 -X ours``. You shouldn't have any merge conflicts
398
-
- Merge current master ``git merge master``; resolve and commit any conflicts
0 commit comments