Skip to content

Conversation

@elijahbenizzy
Copy link
Contributor

[Short description explaining the high-level reason for the pull request]

Changes

How I tested this

Notes

Checklist

  • PR has an informative and human-readable title (this will be pulled into the release notes)
  • Changes are limited to a single goal (no scope creep)
  • Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future TODOs are captured in comments
  • Project documentation has been updated if adding/changing functionality.

@github-actions
Copy link

github-actions bot commented Jan 11, 2026

A preview of is uploaded and can be seen here:

https://burr.dagworks.io/pull/630

Changes may take a few minutes to propagate. Since this is a preview of production, content with draft: true will not be rendered. The source is here: https://github.com/apache/burr/tree/gh-pages/pull/630/

@pjfanning pjfanning added the release-issues Issues affecting releasability of Burr label Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-issues Issues affecting releasability of Burr

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants