Uploaded image for project: 'Operator Ecosystem'
  1. Operator Ecosystem
  2. OPECO-1724

downstream: Sync SDK 1.7.2 downstream

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • 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)
      1. fork https://github.com/openshift/ocp-release-operator-sdk.git 
      2. clone your fork
      3. git remote add openshift https://github.com/openshift/ocp-release-operator-sdk.git
      4. git remote add upstream https://github.com/operator-framework/operator-sdk.git
      5. disable push on openshift:  git remote set-url --push openshift no_push
      6. disable push on upstream:  git remote set-url --push upstream no_push{{}}
      7. That way there is no accidental pushing to the wrong repos{{}}

            rhn-engineering-jesusr Jesus Rodriguez (Inactive)
            rhn-engineering-jesusr Jesus Rodriguez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: