docs: describe the command palette and keyboard shortcut - #719
Open
2160039878-cyber wants to merge 1 commit into
Open
docs: describe the command palette and keyboard shortcut#7192160039878-cyber wants to merge 1 commit into
2160039878-cyber wants to merge 1 commit into
Conversation
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.
Description
The shipped command palette is missing from both feature lists. Add matching entries in README.md and docs/FEATURES.md, naming
Cmd/Ctrl+Kand the tables, connections, saved queries, and actions it exposes.Type of Change
Related Issue
Closes #681
Changes Made
Testing
Compared both additions with
CommandPalette.tsx: its key handler uses(e.metaKey || e.ctrlKey) && e.key === "k", and the listed command groups exist. Reviewed the two-line diff. No executable code changes or new tests.Full Linux validation used the repository's unchanged CI workflow on submitted commit
58d0a24781f191c9eb53db3dcce1d5c9caa18df8: run and logs.bun run test:coverage: 14,713 tests passed, all 391 core test files and 34 component isolation groups passed.bun run coverage:check: 46,324 / 46,324 lines (100%).The fork run's overall status is red solely because SonarCloud Analysis lacks the upstream token/project access. All test/build jobs passed. CLAUDE.md explicitly excludes SonarCloud from required checks, and the upstream workflow skips it for fork PRs. Upstream required workflows still need normal maintainer approval.
Full validation ran on GitHub-hosted Linux: this Windows host cannot run the container-based checks because Docker Desktop fails at inference-manager initialization, and its native full component runner encounters SQLite cleanup
EBUSY. No complete native-Windows pass is claimed.Checklist
Additional Notes
AI-assisted implementation, review, and validation. This branch starts independently from
mainand contains only this issue's change.CI follow-up
The fork-run SonarCloud 401 is tracked in #732 and fixed by #733. The inherited condition admitted fork-owned pushes and fork-local PRs to the canonical SonarCloud project. The dedicated CI fix run now succeeds: all nine executable test/build jobs pass, and SonarCloud is scoped to the canonical repository. That run tests CI fix commit
80a318b; this PR's exact-head verification remains the original run linked above, whose nine executable jobs passed. Upstream Actions still await maintainer approval.