Skip to content

Commit 6d470bb

Browse files
committed
Specify git cherry-pick flags for release process.
Signed-off-by: Andrew Hsu <[email protected]>
1 parent 1dbf3c6 commit 6d470bb

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

project/RELEASE-CHECKLIST.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -71,8 +71,8 @@ We cherry-pick only the commits we want into the bump branch:
7171
# get the commits ids we want to cherry-pick
7272
git log
7373
# cherry-pick the commits starting from the oldest one, without including merge commits
74-
git cherry-pick <commit-id>
75-
git cherry-pick <commit-id>
74+
git cherry-pick -s -x <commit-id>
75+
git cherry-pick -s -x <commit-id>
7676
...
7777
```
7878

@@ -340,7 +340,7 @@ Each time you'll want to produce a new release candidate, you will start by
340340
adding commits to the branch, usually by cherry-picking from master:
341341

342342
```bash
343-
git cherry-pick -x -m0 <commit_id>
343+
git cherry-pick -s -x -m0 <commit_id>
344344
```
345345

346346
You want your "bump commit" (the one that updates the CHANGELOG and VERSION
@@ -494,7 +494,7 @@ and you can check its progress with the CDN Cloudfront Chrome addon.
494494
git checkout master
495495
git fetch
496496
git reset --hard origin/master
497-
git cherry-pick $VERSION
497+
git cherry-pick -s -x $VERSION
498498
git push $GITHUBUSER merge_release_$VERSION
499499
echo "https://github.com/$GITHUBUSER/docker/compare/docker:master...$GITHUBUSER:merge_release_$VERSION?expand=1"
500500
```

0 commit comments

Comments
 (0)