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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Sequential Planner prompt examples #1254

Merged

Conversation

chc273
Copy link
Contributor

@chc273 chc273 commented May 27, 2023

In the skprompt.txt file, the skill _GLOBAL_FUNCTIONS_.SendEmail has one input as recipient while the plan shows the input as email_address.

Contribution Checklist

@github-actions github-actions bot added .NET Issue or Pull requests regarding .NET code kernel Issues or pull requests impacting the core kernel labels May 27, 2023
@lemillermicrosoft lemillermicrosoft enabled auto-merge (squash) May 31, 2023 18:00
@lemillermicrosoft lemillermicrosoft merged commit d095e5a into microsoft:main May 31, 2023
15 checks passed
shawncal pushed a commit to shawncal/semantic-kernel that referenced this pull request Jul 6, 2023
In the `skprompt.txt` file, the skill ` _GLOBAL_FUNCTIONS_.SendEmail`
has one input as `recipient` while the plan shows the input as
`email_address`.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 馃槃
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kernel Issues or pull requests impacting the core kernel .NET Issue or Pull requests regarding .NET code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants