chore: update microsoft-foundry metadata#589
Merged
Merged
Conversation
…name Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: cb64d939-2ee4-4adb-a418-4cd6b6d92959
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: cb64d939-2ee4-4adb-a418-4cd6b6d92959
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: cb64d939-2ee4-4adb-a418-4cd6b6d92959
qinezh
enabled auto-merge (squash)
July 23, 2026 12:04
herohua
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up metadata alignment after the
microsoft-foundryrename (#587) and sync (#588). Three minimal changes, all identity/branding metadata.Changes
microsoft-foundry/.github/plugin/plugin.json) ->Skills and interactive Copilot canvas for designing, configuring, testing and deploying agents to Microsoft Foundry.Alignsplugin.jsonwith the synced extensionpackage.jsondescription (already onmainvia chore: sync microsoft-foundry (db4a09a563a2) #588's sync ofdb4a09a); the sync workflow never touchesplugin.json, so it had the prior wording..github/workflows/sync-microsoft-foundry.yml) ->Sync microsoft-foundry canvas(workflowname:and the job summary heading## Sync microsoft-foundry canvas). No file rename or internal identifier changes.microsoft-foundry/README.md) -># Microsoft Foundry Canvas.No other plugin/canvas display names or unrelated files changed. Vendored payload untouched.
Validation
plugin.jsonand extensionpackage.json-> both descriptions read back byte-exact and identical.yaml.safe_loadon the workflow -> valid;name=Sync microsoft-foundry canvas.Sync Microsoft Foundry/Microsoft Foundry Sync/ prior description text remains in authored files.origin/maincontains only the three intended files.Commits
f4e40a9- chore: update microsoft-foundry plugin description and sync workflow name1ba814a- docs: update microsoft-foundry README title