Repository navigation
docs: clarify that BranchJoiner expects only one branch to produce output per run - #13287
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
julian-risch
approved these changes
Oct 16, 2026
sjrl
enabled auto-merge (squash)
October 16, 2026 06:42
Contributor
Coverage report
This PR does not seem to contain any modification to coverable code. |
This branch was successfully deployed
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
2 participants
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.
Related Issues
Proposed Changes:
BranchJoinerdocstring saying only one connected branch should produce output per run, and pointing toListJoiner/DocumentJoinerfor collecting several branchesBranchJoinerdocs page overviewHow did you test it?
Docs-only change; ran
hatch run fmt.Notes for the reviewer
No release note since this only changes docs.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.