-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add generativeDirectAnswer support #170
Conversation
J=CLIP-1226 TEST=auto,manual added and ran unit test tested in test-site-node, saw appropriate gda response
J=CLIP-1226 TEST=auto,manual added and ran unit test tested in test-site-node, saw appropriate gda response
Pull Request Test Coverage Report for Build 9404901272Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9404910688Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9404918882Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn't note this in search-core, but since this is beta and still in revision process, you may want to merge this into a separate branch instead of main to avoid blocking any (also typically you would merge to develop branch. Update to main is only for when it's time for publishing an official version). You may need to update search-core's develop branch as well (see this PR)
Here would be my suggestion:
- make a fork branch (e.g.
gda-beta
) fromdevelop
- push all your changes to that branch and publish betas from there
- once iterations is done and we are ready to publish to the official version, merge
gda-beta
todevelop
. anddevelop
tomaster
when release cycle come
This would be the flow for all the SDK repos, to avoid blocking hotfixes / official feature updates.
cc @EmilyZhang777 for additional input
Sorry that I missed this on the original PR. |
Pull Request Test Coverage Report for Build 9455766796Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please update this PR to merge to develop instead
Pull Request Test Coverage Report for Build 9470476962Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall LGTM! Just two nits
Pull Request Test Coverage Report for Build 9472519838Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9472688747Details
💛 - Coveralls |
J=CLIP-1226
TEST=auto,manual
added and ran unit test
tested in test-site-node, saw appropriate gda response