Bundle resources reference autogen fixes #2489
Merged
Conversation
This file contains 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
juliacrawf-db
requested review from
pietern,
andrewnester,
shreyas-goenka and
denik
as code owners
juliacrawf-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
ilyakuz-db
approved these changes
Mar 13, 2025
andrewnester
approved these changes
Mar 13, 2025
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.
Changes
Fixes to the bundle reference docgen tool:
Why
In order to make the docgen process seamless, the resources.md file that is generated by the bundle docgen tool needs to create markdown that does not throw doc build errors.
Tests
Tech review, local testing, and creating a docs PR with the generated reference.md and resources.md files.