Copilot Studio and Agents - repo structures and relationships #76
cleemullins
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem Statement
Today there are numerous Copilot Studio, M365 Agents SDK and Bot Framework repos. The proliferation of repos has lead to obsolete samples, obsolete technologies, and obsolete documentation. The lack of clear repo ownership of repos also leads to Issues and PRs stagnating.
Search Engines are returning incorrect and obsolete results. Developers are unable to find what they're looking for or end up working with incorrect and obsolete technologies.
North Star
A set of quality GitHub Repos focused on the following:
Proposed Organization
A Hub/Spoke model is proposed, as the Hub will be a starting point for finding content, hosting core specs and documentation, and hosting samples.
M365 Agents SDK
This is the top-level GitHub repo, and the focus of our pro code development. This repo hosts:
Links from here go to:
Update this repo's readme to have details around Pro Code Development for Copilot Studio. Extend the Github pages with these docs as well.
Bot Framework SDK Changes
The Bot Framework SDK get "Superseded by" messages along with links to the root M365 Agents Repo and specific language repo. Anyone who lands on these repos should be aware of the newer repos and tech stacks.
Copilot Studio Samples Repo
The following changes are suggested for (Copilot Studio Samples)[https://github.com/microsoft/CopilotStudioSamples]:
Beta Was this translation helpful? Give feedback.
All reactions