Skip to content

Updated AI Toolkit for Visual Studio Code with instructions. #476

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

Merged
merged 2 commits into from
Aug 11, 2025

Conversation

Adolfi
Copy link
Contributor

@Adolfi Adolfi commented Jul 3, 2025

The current "AI Toolkit for Visual Studio Code" section under "Foundry Local architecture" mentions that it is possible to setup Foundry local model in AI Toolkit, but no actual guide or instructions.

In this PR I've added Prerequisites and instructions for how to setup AI Toolkit against your locally running Foundry Local service.

The "AI Toolkit for Visual Studio Code" section under "Foundry Local architecture" mentions that it is possible to setup Foundry local model in AI Toolkit, but no actual steps or instructions.

In this PR I've added Prerequisites and instructions for how to setup AI Toolkit against your locally running Foundry Local service.
Copy link
Contributor

@Adolfi : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 50424aa:

✅ Validation status: passed

File Status Preview URL Details
articles/ai-foundry/foundry-local/concepts/foundry-local-architecture.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@jonburchel

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Jul 3, 2025
@v-dirichards
Copy link
Contributor

@jonburchel Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

@jonburchel
Copy link
Contributor

@samuel100 can you review this PR to be sure it is correct, and if so, we can sign-off on it. Since it was submitted from the public repo want to make sure you have a chance to look it over before we merge. Thank you!

@v-dirichards
Copy link
Contributor

#assign: @samuel100

Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Jul 29, 2025
@Adolfi
Copy link
Contributor Author

Adolfi commented Jul 29, 2025

?

@github-actions github-actions bot removed the inactive This PR is inactive for more than 14 days label Jul 30, 2025
@v-dirichards
Copy link
Contributor

@samuel100 Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

@ttorble
Copy link
Contributor

ttorble commented Aug 11, 2025

I sent email to @samuel100 today.

@MicrosoftDocs/public-repo-pr-review-team

@samuel100
Copy link
Contributor

#sign-off

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @jonburchel

Copy link
Contributor

Learn Build status updates of commit eb5c224:

✅ Validation status: passed

File Status Preview URL Details
articles/ai-foundry/foundry-local/concepts/foundry-local-architecture.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards merged commit 78a267e into MicrosoftDocs:main Aug 11, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants