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
chore: Rebase against upstream #338
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix #207450 * Fix #207432 * Fix #207442 Fix #207434
* add message to AI search results * don't run search if no search results
…lPushStackEleChangesAPI pushStackElement API in NB Model to be same as same API in Text Model
Reduce volume of inputlatency events to 1% of users
* pushStackElement API in NB Model to be same as same API in Text Model * More meaningful timeline entries for Notebooks
add `ChatLocation` so that chat participants can contribute to terminal chat
…at to work on Windows (#202762) * Do not prefix autoImportFileExcludePatterns with `/` * Fix autoImportFileExcludePatterns format
…ed locations to the cursor navigation histories. (fix #207484) (#207561)
* hide inline chat content widget on blur * use message controller to show session creation failure
…andidate focus changes or one is selected
* move sparkle to input * cleanup
Fix terminal chat input background
Adopt buttonConfigProvider for terminal chat actions
From the user's perspective: * Now the cmd/alt+up/down keybindings that cycle through separators have the following behavior: * if a separator is visible, just reveal it without messing with scroll top * if a separator is not visible, scroll it up to the top of the view * When the active item, or your mouse, is over an item, the actions on that section's separator are also visible Code perspective: * Separate separators & regular items into their own renderers (there's more to clean up here, but a good start) * Allow the renderers to know which items are visible and expose that (so that we can determine which separator to show actions on) * Folded revealing an item into the focus function for ease * Simplified the call to `setElements` to be used in "tree-like" scenarios or "list-like" scenarios
vscode-upstream-sha1: 770afe0 rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Signed-off-by: Roman Nikitenko <rnikiten@redhat.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Signed-off-by: Roman Nikitenko <rnikiten@redhat.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED
Pull Request Dev image published: |
Pull Request Che-Code image published: |
RomanNikitenko
requested review from
azatsarynnyy,
vitaliy-guliy and
l0rd
as code owners
March 19, 2024 12:07
azatsarynnyy
approved these changes
Mar 19, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Rebase against the upstream
What issues does this PR fix?
eclipse-che/che#22884
How to test this PR?
Does this PR contain changes that override default upstream Code-OSS behavior?
git rebase
were added to the .rebase folder