2.6 KiB
Connections
Link to the issues addressed by this PR, or dependent PRs in other repositories
When one pull request builds on another, please put "Depends on #NNNN" towards the top of its description. This helps maintainers notice that they shouldn't merge it until its ancestor has been approved. Don't use draft PR status to indicate this.
Description
Describe what problem this is solving, and how it's solved.
Testing
Explain what you have done to ensure this change is adequately tested (e.g. adding test cases, running tests on an unusual platform, or manually checking visual results).
Squash or Rebase?
If your pull request contains multiple commits, please indicate whether
they need to be squashed into a single commit before they're merged,
or if they're ready to rebase onto trunk as they stand. In the
latter case, please ensure that each commit passes all CI tests, so
that we can continue to bisect along trunk to isolate bugs.
LLM Use?
Let us know how you used LLMs for this PR. This helps us understand the classes of issues we should look for. LLM use is allowed, but we ask that you understand all the code you submit and treat it as your own. We do ask that any significant descriptions be written by hand.
Checklist
- I self-reviewed and fully understand this PR.
CHANGELOG.mdentries for the user-facing effects of this change are present.- The PR is minimal, and doesn't make sense to land as multiple PRs.
- Commits are logically scoped and individually reviewable.
- The PR description has enough context to understand the motivation and solution implemented.
- (If applicable) WebGPU implementations built with
wgpumay be affected behaviorally. - (If applicable) Validation and feature gates are in place to confine behavioral changes.
- (If applicable) Tests demonstrate the validation and altered logic works.