Wondering what I'm doing at Microsoft? I've joined the @azureadvocates Developer Relations team here in Australia.
If you run a community, startup or are a student looking for support, reach out ๐
Please welcome @slace as a new member of the Microsoft @azureadvocates Developer Relations team who will be supporting developer communities, students & startups in Australia & globally. #devrel
This week: go beyond chat and start architecting AI agent workflows.
Explore GitHub Canvas, context engineering, token consumption, MCP integrations + custom Copilot plugins with Microsoft Reactor.
Save your spot: https://t.co/zWxvzcSzVv
#AIGenius#GitHub#AI
As traffic grew exponentially, we moved 99.99999% of GitHub's Git repos to Azure. A new write path moves the last, busiest repos, keeps cross-region round trips from capping throughput, and enables stateless Azure Blob Storage replicas. https://t.co/arMfnIfx0o
@QuinnyPig yeah, wsl is kinda awesome, with plain distro running CLI, or WSLg for launching GUI apps, and now WSLc for containers without needing Docker (they also get GPU support).
Plus MXC for sandboxing is pretty cool
@burkeholland@github Better off providing the website link, https://t.co/z6KJ470ecF, as there is a nice Install button you can click that will open Copilot app and trigger the install flow
Get ready to make smarter Al decisions with @slace, Principal Developer Advocate, Microsoft!
Learn how to optimise tokens, make the most out of Github Copilot and build tailored experiences at AI Genius Season 6: https://t.co/D7cqbMi4jn
@MSFTReactor
@Aaronontheweb Marketplaces aren't that useful, unless you're hosting multiple plugins in a single repo. Most harnesses have some kind of `<harness> plugin install name@github-repo` design, no marketplace needed.
If you want to list in a marketplace, we can do that from Awesome Copilot
@Aaronontheweb Marketplaces are not (yet) defined as part of the spec, but so far most harnesses are mostly aligned.
I meant having a root plugin.json following https://t.co/pEd0lneojc.
That removes the need for vendor-specific plugin.json files and consistency across vendor harnesses