File tree Expand file tree Collapse file tree 1 file changed +10
-7
lines changed Expand file tree Collapse file tree 1 file changed +10
-7
lines changed Original file line number Diff line number Diff line change @@ -90,20 +90,23 @@ Backports
90
90
When doing backports please include the branch you backported the
91
91
commit to along with the SHA in a comment on the original PR.
92
92
93
- Assuming we have ``matplotlib `` as a read-only remote to the
94
- matplotlib/matplotlib repo and ``DANGER `` as a read/write remote to
95
- the matplotlib/matplotlib repo, we do a backport from master to 2.x.
93
+ We do a backport from master to v2.0.x assuming:
94
+
95
+ * ``matplotlib `` is a read-only remote branch of the matplotlib/matplotlib repo
96
+
97
+ * ``DANGER `` is a read/write remote branch of the matplotlib/matplotlib repo
98
+
96
99
The ``TARGET_SHA `` is the hash of the merge commit you would like to
97
100
backport. This can be read off of the github PR page (in the UI with
98
101
the merge notification) or through the git CLI tools.::
99
102
100
103
git fetch matplotlib
101
- git checkout v2.x
102
- git merge --ff-only matplotlib/v2.x
104
+ git checkout v2.0. x
105
+ git merge --ff-only matplotlib/v2.0. x
103
106
git cherry-pick -m 1 TARGET_SHA
104
- gitk # to look at it
107
+ git log --graph --decorate # to look at it
105
108
# local tests? (use your judgment)
106
- git push DANGER v2.x
109
+ git push DANGER v2.0. x
107
110
# leave a comment on PR noting sha of the resulting commit
108
111
# from the cherry-pick + branch it was moved to
109
112
You can’t perform that action at this time.
0 commit comments