Skip to content
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

Remove unneeded deployment #540

Merged
merged 1 commit into from
Aug 17, 2023
Merged

Remove unneeded deployment #540

merged 1 commit into from
Aug 17, 2023

Conversation

pamelafox
Copy link
Collaborator

Purpose

This PR removes the GPT deployment that we aren't currently using it, since it is redundant with the ChatGPT deployment (same model, gpt-35-turbo). We might use a different deployment in future if instruct becomes available and works well for query generation, but in the meantime, the additional deployment is confusing folks.

Also, while testing this, I discovered the two optional Ask approaches do not work with the Chat Completions API - they only work with the completions API, but 0613 doesn't support completions and is the only version that can be deployed newly now. I'll file that as an issue.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[X] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

  • azd up
  • start server locally

@srbalakr
Copy link
Collaborator

I was working on to make a PR. Thank you.

@pamelafox pamelafox merged commit fb3aa0a into Azure-Samples:main Aug 17, 2023
5 checks passed
@pamelafox pamelafox deleted the remove-gpt branch August 17, 2023 18:06
HughRunyan pushed a commit to RMI/RMI_chatbot that referenced this pull request Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants