🤖 Auto-merge documentation from branches - #2151
Merged
Merged
Conversation
Generated from branches-config.json at - Merged documentation from multiple branches - Generated unified docs.json - Updated assets and content structure
buger
added
auto-deployment
automated
documentation
buger
enabled auto-merge (squash)
May 21, 2026 12:05
|
Failed to generate code suggestions for PR |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
📚 Documentation Merge Summary
This PR contains automatically merged documentation from multiple branches.
Triggered by:
Deployment Details:
branches-config.json(root deployment)Changes Include:
docs.jsonconfiguration🚦 This PR will be processed by merge queue to ensure proper validation and ordering.
Previous deployment PRs have been automatically closed to prevent conflicts.