From ac8e6331e858384cd096ceb9a0ead9b80fb0a908 Mon Sep 17 00:00:00 2001 From: Bharath Vedartham Date: Sun, 21 Feb 2021 21:32:54 +0530 Subject: Add docs about github tokens for cherrypicking --- contributors/devel/sig-release/cherry-picks.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/contributors/devel/sig-release/cherry-picks.md b/contributors/devel/sig-release/cherry-picks.md index 77335df6..43a68b10 100644 --- a/contributors/devel/sig-release/cherry-picks.md +++ b/contributors/devel/sig-release/cherry-picks.md @@ -27,6 +27,7 @@ branches. - Have `hub` installed, which is most easily installed via `go get github.com/github/hub` assuming you have a standard golang development environment. +- A github token which has permissions to create a PR in an upstream branch. ## What Kind of PRs are Good for Cherry Picks @@ -89,6 +90,11 @@ patch release branches. release you want to cherry pick to. Cherry picks should be applied to all [active](https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md#detailed-release-history-for-active-branches) release branches where the fix is applicable. + + - When asked for your github password, provide the created github token + rather than your actual github password. + Refer [https://github.com/github/hub/issues/2655#issuecomment-735836048](https://github.com/github/hub/issues/2655#issuecomment-735836048) + - Your cherry pick PR will immediately get the `do-not-merge/cherry-pick-not-approved` label. -- cgit v1.2.3