Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions doc/contributing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -389,14 +389,14 @@ each time you commit changes. You can skip these checks with
conflicts. Because they have had limited testing, please reach out to the core devs
on your pull request if you face any issues, and we'll help with the merge:

- Merge the commit on master prior to the `black` commit into your branch
`git merge f172c673`. Any conflicts are real conflicts and require resolving
- Apply `black .` to your branch and commit
# TODO: insert after the black commit is on master
- Merge master at the `black` commit, resolving in favor of 'our' changes:
`git merge [master-at-black-commit] -X ours`. You shouldn't have any merge conflicts
- Merge current master `git merge master`; any conflicts here are real and
again require resolving
- Merge the commit on master prior to the ``black`` commit into your branch
``git merge f172c673``. If you have conflicts here, resolve and commit.
- Apply ``black .`` to your branch and commit ``git commit -am "black"``
- 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 -``
- Commit (``git commit -am "black2"``)
- Merge master at the ``black`` commit, resolving in favor of 'our' changes:
``git merge d089df38 -X ours``. You shouldn't have any merge conflicts
- Merge current master ``git merge master``; resolve and commit any conflicts

Backwards Compatibility
~~~~~~~~~~~~~~~~~~~~~~~
Expand Down