Repository navigation
Move public search scope into the Documents picker - #1741
Merged
Paul Lizer (paullizer) merged 1 commit intoOct 9, 2026
Merged
Paul Lizer (paullizer) merged 1 commit into
Paul Lizer (paullizer) merged 1 commit into
Conversation
Place aggregate public scope choices in the existing Documents picker while preserving the public directory handoff and Orchestrate manual-controls placement. Add regression coverage and update the V2 documentation and version. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Oct 9, 2026
431f533
into
microsoft:paullizer-react-v2-ui
11 checks passed
This file contains hidden or 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
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.
Summary
Linked issue
Refs #1722 (aggregate public chat row; this PR covers scope-control placement only)
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedTesting / validation
npm --prefix .\application\v2_ui run build- passed (existing bundle-size warning remains).python -m pytest .\functional_tests\test_v2_chat_context_picker.py .\functional_tests\test_v2_public_chat_scope.py -q --disable-warnings- 38 passed.python -m pytest .\ui_tests\test_v2_public_chat_scope.py .\ui_tests\test_v2_public_directory.py .\ui_tests\test_v2_chat_context_selection.py -q- 125 passed.python .\ui_tests\test_v2_orchestration_composer.py- 7 checks passed.python .\functional_tests\test_docs_app_surface_coverage.py- 7 checks passed;python .\functional_tests\test_docs_site_quality.py- 6 checks passed.node "C:\Users\paullizer\AppData\Roaming\com.github.githubapp\app-skills\impeccable\scripts\detect.mjs" --json .\application\v2_ui\src\components\chat\Composer.tsx .\application\v2_ui\src\components\chat\ComposerEditor.tsx .\application\v2_ui\src\components\chat\DocumentPickerPopover.tsx- no deterministic findings. Reviewed local Chromium screenshots at 1440px and 390px in light/dark themes with long configured workspace labels; the production Azure app was not changed or tested.git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check- passed.Documentation
Release notes were left unchanged; this interaction cleanup does not introduce a separately advertised feature.
Security checklist
@swagger_route(security=get_auth_security())(no Flask routes added)sanitize_settings_for_user()(no settings payloads added)