GitHub Copilot Dev Days: what the community event kit actually contains

What the Dev Days repository is for, and who it is aimed at

This is not a library, a CLI or a Copilot extension. It is an event kit. The README describes GitHub Copilot Dev Days as a global, in-person user group initiative running from March 15th to May 15th 2026, with sessions of roughly three hours built around hands-on, AI-assisted coding with GitHub Copilot. The audience is narrow and specific: community leaders who want to host one of those sessions. The repository says so directly, framing itself as containing everything needed to plan, organize and promote an event.

That framing matters when you evaluate it. A developer looking for something to install has the wrong repository. The material a developer would want, the hands-on labs, is published on a separate site, copilot-dev-days.github.io, which the README calls the central site where all Dev Days workshops are published. The repository is the back office for that site, not the site itself.

The README also carries a notice at the top stating that the Dev Days content has moved and linking to a dev-days repository for the new page. So the repository is a 2026 event kit whose own README redirects readers elsewhere for current content. That is the single most important thing to understand before cloning it.

Repository layout: organization, content, marketing, assets

The top level tells you what the kit is made of. Alongside README.md, LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, EVENT_CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md and SWEEPSTAKES.md, there are four content directories: organization, content, marketing and assets.

The README maps three of them to concrete resources. The organization directory holds practical guidance to plan and run an event from start to finish, described as an event checklist and a registration page draft. The content directory holds technical content for sessions and workshops, described as presentation slides and hands-on labs, and the README distinguishes an organizer view (the repository directory) from an attendee view (the published site). The marketing directory holds materials to promote the event, described as social media templates and event covers. The assets directory holds images such as the banner referenced at the top of the README.

There is no build system, no package manifest and no test suite visible in the layout. The primary language is listed as unknown, which fits a repository that is mostly Markdown, slides and image files. Treat the directories as a document bundle with a fixed structure: if you fork it, the value is in the text and the decks, not in anything executable.

Two event formats and the three-hour session shape

The README recommends one of two formats depending on your community's experience, audience and available infrastructure. The sessions-only format is technical talks and demos around GitHub Copilot. The sessions plus workshop format adds a hands-on workshop for deeper practical learning. Both are described as interactive and hands-on, encouraging participants to learn by doing.

The distinction is more than scheduling. A sessions-only event can run with a room, a screen and speakers. A sessions plus workshop event needs attendees to have working environments and needs the labs from the published site to run against them. The README does not document lab prerequisites, machine setup or troubleshooting for the workshop format, and that gap is worth knowing about before you commit to it: the organizer guide is the place to look, and the README itself does not reproduce its contents.

The roughly three-hour session length is the other fixed constraint. It appears once, in the description of the series, and shapes how much of the content directory you can realistically use in one sitting.

Getting the kit onto your machine and finding the right entry point

There are no install steps in the README, because there is nothing to install. What you can do is clone the repository and read the organization guide first, then open the content directory for slides and labs. The commands below are a plain Git clone and a directory listing; they are the only setup this repository supports.

git clone https://github.com/github/GitHub-Copilot-Dev-Days.git
cd GitHub-Copilot-Dev-Days
ls

You should see the top-level entries listed above: organization, content, marketing, assets and the governance files. The next step is to read the organization directory, which the README describes as the event checklist and registration page draft.

ls organization
ls content
ls marketing

Those listings are how you confirm what the kit actually ships before you build a plan around it. For attendees rather than organizers, the README gives a different instruction: send them to copilot-dev-days.github.io, where the workshops are published. The README also points questions at the repository's Discussions area, and links a contributing guide for when to use Discussions.

Where the kit stops: content that has moved and events that are closed

The clearest limitation is stated in the README itself. The top notice says the Dev Days content has moved and links to a dev-days repository for the new page. The README also says this round of Dev Days is closed for new events. Those two sentences together mean the repository is a record of a completed planning cycle, not an open call. If you arrived looking for how to host an event now, the answer is in the linked repository, not here.

A second limitation is that the repository is not a Copilot tutorial. Nothing in the README teaches Copilot usage; the labs live on the published site. If your goal is to learn the tool, the kit is the wrong artifact.

A third is governance overhead. The repository carries a code of conduct, an event code of conduct, a security policy, a support file and a sweepstakes file. That is normal for a Microsoft-run community program, but it means a fork inherits documents written for a specific program, including trademark guidance stating that use of Microsoft trademarks in modified versions must not imply Microsoft sponsorship. The README's trademark section is explicit that authorized use of Microsoft marks must follow Microsoft's Trademark & Brand Guidelines.

What this kit is not, compared with running your own workshop repo

The real alternative is not another event kit; it is building your own workshop repository. The difference in approach is ownership of the content pipeline. With Dev Days, the slides, labs and marketing templates are maintained centrally, and your job is to adapt them to a local audience. The upside is that you start from material that has already been through a program review, including the code of conduct and sweepstakes files. The downside is that you inherit the program's calendar, its branding rules and its publication site: attendees are directed to copilot-dev-days.github.io rather than to anything you control.

A self-built repository inverts that. You own the schedule, the branding and the hosting, and you write the labs. For a meetup that wants to teach Copilot on its own terms and keep running past May 2026, that is the more durable path. For a group that wants a three-hour session in the March 15 to May 15, 2026 window with minimal preparation, the kit is the shorter route. The trade-off is not quality; it is who decides what the room sees.

Licence, maintenance and what a fork costs you

The repository is MIT licensed, which is permissive and places few conditions on reuse of the contents. That licence does not cover the trademarks, and the README separates the two questions: it states that use of Microsoft trademarks or logos in modified versions must not cause confusion or imply Microsoft sponsorship, and that third-party trademarks follow their owners' policies. Anyone forking the marketing directory should read that section before publishing event covers and social templates, because those are exactly the assets most likely to carry a logo. This is a description of what the README says, not legal advice.

On maintenance, the last push was on 2026-08-13. The repository is not archived. There are no releases retrieved, which is consistent with a document bundle rather than a versioned product. Upgrade cost is therefore low in the software sense and high in the editorial sense: there is no dependency graph to update, but if the program moves its content again, as the top notice shows it already has, your fork drifts from the canonical material and you have to reconcile it by hand.

Editorial conclusion

Adopt this kit if you are a community leader planning a Copilot session and you want slides, labs and promotion templates that already exist rather than writing them yourself. Do not adopt it if you want a working Copilot demo environment or a self-hosted workshop platform; the repository is documents and assets, and the README points attendees at copilot-dev-days.github.io for the labs instead. Before you plan anything, check that your event window falls inside March 15 to May 15, 2026, and read the moved-content notice at the top of the README, because this round is closed to new events and the current Dev Days page lives in a different repository.

Frequently asked questions

Official sources

1. github/GitHub-Copilot-Dev-Days on GitHub
2. Issues
3. License: MIT
4. Project website
5. README