docs: include-tool-results-in-member-responses #535
Open
ashpreetbedi wants to merge 1 commit intomainfrom
Open
docs: include-tool-results-in-member-responses #535ashpreetbedi wants to merge 1 commit intomainfrom
ashpreetbedi wants to merge 1 commit intomainfrom
Conversation
shaloo
force-pushed
the
includ-tool-results-in-member-responses
branch
from
1705a16 to
828e12e
Compare
Contributor
|
Merge approvals, schedules changes from the main branch before reviewing this commit. |
Contributor
|
reference files should ideally be updated via API ref re-generation at build time. These generated files should not be checked into the repo sources. Thoughts? @ysolanky |
Contributor
|
Also, docs.json needs to be updated here - not sure why it wasn't in the first place. Just checking before adding it in docs.json file. context/team/overview |
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.
Description
Describe key changes, mention related issues or motivation for the changes.
Note: Your PR title must follow conventional commit format (e.g.,
docs: add auth guide,fix: correct broken links,style: update formatting). See CONTRIBUTING.md for details.Type of Change
Related Issues/PRs (if applicable)
Checklist