XComp commented on PR #23235: URL: https://github.com/apache/flink/pull/23235#issuecomment-1691084506
You should be allowed to fork the entire repo. You would clone the repo then and add Flink's upstream repository as a remote location: ``` # this creates a remote reference "origin" by default $ git clone https://github.com/mimaomao/flink $ git remote add upstream https://github.com/apache/flink $ git fetch upstream $ git checkout -b FLINK-32869-1.18 upstream/release-1.18 $ git cherry-pick <commit-sha> # This pushes your local branch FLINK-32869-1.18 to your forked repo that is referenced under origin (compare with the clone command above) $ git push origin FLINK-32869-1.18 ``` Then you can create a dedicated PR in Github as usual. Keep in mind to set the correct base branch in the corresponding PR (it's set to `master` by default). This would need to be done for `release-1.18` (which was created two days ago), `release-1.17` and `release-1.16`. Another remark: You added your change in your fork's `master` branch which is kind of unusual. You would create a dedicated branch for the change and push that to your fork (i.e. `origin`), instead. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
