-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add commands for alignment che-code with upstream #427
Conversation
Signed-off-by: RomanNikitenko <rnikiten@redhat.com>
Pull Request images published ✨ Editor: quay.io/che-incubator-pull-requests/che-code:pr-427-amd64 |
Build 3.18 :: code_3.x/1478: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7790: Console, Changes, Git Data |
Build 3.18 :: push-latest-container-to-quay_3.x/4969: Console, Changes, Git Data |
Build 3.18 :: get-sources-rhpkg-container-build_3.x/7797: code : 3.x :: Build 64881015 : quay.io/devspaces/code-rhel8:3.18-2 |
Build 3.18 :: update-digests_3.x/7720: Console, Changes, Git Data |
Build 3.18 :: code_3.x/1478: Upstream sync done; /DS_CI/sync-to-downstream_3.x/7790 triggered |
Build 3.18 :: operator-bundle_3.x/3655: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7794: Console, Changes, Git Data |
Build 3.18 :: push-latest-container-to-quay_3.x/4970: Console, Changes, Git Data |
Build 3.18 :: copyIIBsToQuay/2833: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7794: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.x/7801 triggered; /job/DS_CI/job/dsc_3.x triggered; |
Build 3.18 :: operator-bundle_3.x/3655: Upstream sync done; /DS_CI/sync-to-downstream_3.x/7794 triggered |
Build 3.18 :: update-digests_3.x/7720: Detected new images: rebuild operator-bundle |
Build 3.18 :: dsc_3.x/2015: Console, Changes, Git Data |
Build 3.18 :: dsc_3.x/2015: 3.18.0-CI |
Build 3.18 :: copyIIBsToQuay/2833: 3.18 |
What does this PR do?
Add commands to the devfile to help with alignment che-code with upstream
What issues does this PR fix?
eclipse-che/che#22578
How to test this PR?
As result you can get the following state:
or
Both states are expected - as it's depends on the current state of che-code and vscode repos.
Does this PR contain changes that override default upstream Code-OSS behavior?
git rebase
were added to the .rebase folder