We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
name: Feature request about: Suggest an idea for this project
OpenAI o1 model introduced a number of unique parameters incompatible with other models (1) :
With o1 being released as GA we need to add the model support as soon as reasonable.
This overlaps with Bug report (2).
The text was updated successfully, but these errors were encountered:
Original issue: microsoft/semantic-kernel#10015
Sorry, something went wrong.
Hi team, I'd like to start contributing to this repo and was planning to look into this issue. I've read the documentation: https://learn.microsoft.com/en-us/semantic-kernel/support/contributing?tabs=Java&pivots=programming-language-java
Are there any other guidelines or processes I should review before getting started?
Hi team, I'd like to start contributing to this repo and was planning to look into this issue. I've read the documentation: https://learn.microsoft.com/en-us/semantic-kernel/support/contributing?tabs=Java&pivots=programming-language-java Are there any other guidelines or processes I should review before getting started?
Hi @cristhiank - that would be most welcome! At some point you'll be asked to sign the Microsoft CLA, but that should occur as part of the PR process.
Thanks @karianna ! I've already forked the repo and started ramping up. Hoping to send an initial PR soon!
No branches or pull requests
name: Feature request
about: Suggest an idea for this project
OpenAI o1 model introduced a number of unique parameters incompatible with other models (1) :
With o1 being released as GA we need to add the model support as soon as reasonable.
This overlaps with Bug report (2).
The text was updated successfully, but these errors were encountered: