Open
Conversation
This commit introduces workflow_dispatch inputs for specifying branch names or tags for multiple repositories in the CI pipeline. It enables flexibility for testing specific versions of dependencies, with defaults set to 'main.' Additionally, a conditional check ensures local publishing to GitHub Pages based on input or event type.
Update ci for workflow build
update to test the empty list fix in the index.
Collaborator
Author
Implemented parsing logic to resolve repository and reference overrides for multiple dependencies dynamically based on inputs. Updated checkout steps to use resolved values, improving flexibility and maintainability.
- Restored intuitive “type‑ahead” results for underscore/hyphenated terms (e.g., Vulkan extension names) without changing the index format. - Begins‑with fallback: if a query term contains `_` or `-`, we now use the raw lowercased prefix (`original + '*'`, pipeline disabled) so composite tokens like `vk_nv_copy` match early during incremental typing (`vk`, `vk_`, `vk_nv`, …). - Contains fallback: continues to use a normalized/stemmed last segment substring (`*segStem*`, pipeline disabled) for robust matching across inflections while keeping recall. - Preserved previous fixes: - Case‑insensitive wildcard matching. - Vendor‑order retry (`NV_VK_*` ↔ `VK_NV_*`) only on zero results. - Split‑index rendering guard: no blank rows; show a single “No results found …” dataset when there are no hits. - Index‑side fallbacks ensure non‑empty `title` and `text` in all docs.
- Segment‑aware wildcard search for underscore/hyphen tokens - Begins‑with fallback: if a query term contains `_` or `-`, use the raw, lower‑cased composite prefix (`original + '*'`) so partial typing like `vk_nv_c`, `vk_nv_copy`, `vk_nv_copy_mem` yields matches early. - Contains fallback: use the last segment’s normalized/stemmed token with leading/trailing wildcards (`*seg*`) to match inflections like `copy`→`copi`. - Case‑insensitivity preserved; pipeline is bypassed for wildcard phases but we pre‑normalize as needed. - Stabilized results for underscore/hyphen queries - Skip trie prefiltering when the input contains `_` or `-` to avoid over‑restrictive candidate pruning that caused result churn during incremental typing. - Ranking improvements - Increased field boost for `name` (page/extension name) so extension pages rank above general mentions: `name: 15`, `title: 10`, `keyword: 5`. Also mirrored this boost in the temporary filtered index. - Vendor‑order retry retained - Zero‑result safety net re‑tries `NV_VK_*` ↔ `VK_NV_*` queries once (allow‑listed vendors), unchanged.
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
1 participant
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.
DO NOT MERGE THIS DIRECTLY.
This points back to a PR repo under review. When the index changes in antora-lunr-extension are merged from my repo, then update to point at that commit and then merge.