mirror of
https://github.com/kyverno/kyverno.git
synced 2025-03-05 07:26:55 +00:00
docs(contributing): add how to cherry-pick section (#4127)
Signed-off-by: Batuhan Apaydın <batuhan.apaydin@trendyol.com>
This commit is contained in:
parent
24e96884c5
commit
d05a0759ca
1 changed files with 30 additions and 1 deletions
|
@ -90,8 +90,37 @@ Go ahead and push your changes to GitHub using this command.
|
|||
```sh
|
||||
git push
|
||||
```
|
||||
|
||||
#### Developer Certificate of Origin (DCO) Sign off
|
||||
=======
|
||||
## Cherry-pick PRs to release branches
|
||||
|
||||
Once you fork the project, you will notice that there are a number of branches related to Kyverno's releases such as release-1.7. You can view the list of remote branches by using the command below:
|
||||
|
||||
```sh
|
||||
$ git branch -r
|
||||
...
|
||||
origin/release-1.5
|
||||
origin/release-1.6
|
||||
origin/release-1.7
|
||||
```
|
||||
|
||||
Checkout one of the release branch and cherry-pick the PRs you want to merge into the release branch:
|
||||
|
||||
```sh
|
||||
$ git checkout release-1.7
|
||||
|
||||
git cherry-pick <commit-hash> -s
|
||||
|
||||
git push --set-upstream origin release-1.7
|
||||
```
|
||||
|
||||
Once the commit has been cherry picked, the author will need to open a PR merging to the release branch, release-1.7 for example.
|
||||
|
||||
## Engage with us
|
||||
|
||||
The website has the most updated information on [how to engage with the Kyverno community](https://kyverno.io/community/) including its maintainers and contributors.
|
||||
|
||||
## Developer Certificate of Origin (DCO) Sign off
|
||||
|
||||
For contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project, we are requiring everyone to acknowledge this by signing their work which indicates you agree to the DCO found [here](https://developercertificate.org/).
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue