📖 [Docs]: Reusable pipeline prefetch specification - #667
Draft
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Draft
📖 [Docs]: Reusable pipeline prefetch specification#667Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Conversation
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
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.
Pipeline prefetch has a reusable specification and design, with GitHub as the first adoption profile. These documents describe intended behavior for discussion, not a released feature. This is documentation only: no runtime behavior changes.
The contract specifies automatic prefetch for eligible paginated result producers with an explicit opt-out, while preserving ordered streaming output, request policies, bounded lookahead, cancellation, and context isolation. It does not make every pipeline-input command concurrent or change mutation, consumer, or raw GraphQL query behavior.
Technical details
index.md,spec.md,design.md, andimplementation.mdtogether underdocs/pipeline-prefetch/, plus README navigation. Document bodies are preserved; frontmatter usesms.titleto fit the existing Markdown rules and framework convention.-NoPrefetchand one future page by default, counting queued, producer-held, and in-flight pages together. This is distinct from the prototype's node-countQueueCapacity. Adoption covers all eligible REST and GraphQL list paths, not only repository connections.mainURL becomes available when this PR is merged; links between the four pages are relative. No site configuration, build tooling, or runtime files change.Implementation scope: only the documentation and navigation are delivered. This branch is based independently on
main, not stacked on #645. Related-work review is limited to #644 and #645; neither is completed or closed by this change.Validation: the existing Markdown linter passes for all five changed files, and the existing codespell configuration passes for the four new documents. The nine relative document links, README target, requirement/scenario completeness, immutable source references, and staged diff were inspected. No module tests or full module/site build were run for this documentation-only change.
docs/pipeline-prefetch/*.mdREADME.mdThis PR remains draft for discussion. CI, automated PR review, and other ready-for-review gates are not represented as complete. Auto-merge is not enabled.
Relevant issues (or links)
Related work