-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
1
-
False
-
False
-
Undefined
-
-
OSDK Sprint 59
I would like someone other than Jesus to sync upstream SDK with downstream.
The steps to sync a release are defined in the downstream readme:
https://github.com/openshift/ocp-release-operator-sdk#syncing
Acceptance criteria:
- PR against downstream repo
- passing downstream CI
My setup looks as follows:
openshift https://github.com/openshift/ocp-release-operator-sdk.git (fetch) openshift no_push (push) origin git@github.com:jmrodri/ocp-release-operator-sdk.git (fetch) origin git@github.com:jmrodri/ocp-release-operator-sdk.git (push) upstream https://github.com/operator-framework/operator-sdk.git (fetch) upstream no_push (push)
- fork https://github.com/openshift/ocp-release-operator-sdk.git
- clone your fork
- git remote add openshift https://github.com/openshift/ocp-release-operator-sdk.git
- git remote add upstream https://github.com/operator-framework/operator-sdk.git
- disable push on openshift: git remote set-url --push openshift no_push
- disable push on upstream: git remote set-url --push upstream no_push{{}}
- That way there is no accidental pushing to the wrong repos{{}}
- blocks
-
OPECO-1753 [downstream] openshift specific plugin
- Closed
- relates to
-
OCPPLAN-7778 Operator-SDK becomes a supported offering
- Closed