No. Due to the overwhelming response to the Dev Days program, we have reached capacity and are no longer accepting or approving new event submissions.
Dev Days is a global series of community-led in-person events focused on product awareness and adoption of GitHub's key products, with the focus on GitHub Copilot app and Copilot CLI.
Events run from September 1 through October 31, 2026.
Community leaders, GitHub Stars, MVPs, and other developers can organize Dev Days events. The program activates these community members to host and run events in their local areas.
The program team will provide you an event page on the Luma calendar based on the date provided when you signed up to host an event. From there, you can update the page details to make the most sense for your event.
Yes, you can host multiple events as long as they are for different audiences, dates, and/or in different cities.
You will need to fill out one registration form for each event you plan to run.
Yes, you can run an additional event in the same city if the events are sufficiently different. Questions to consider:
- Do these events cover the same topics?
- Do they reach the same audience? For example, you may plan to run an event specifically for your user group or school.
- Are the event dates too close?
If the events would be too similar, we suggest reaching out to collaborate with the existing event. If you have any questions about your prospective event, you can reach out to us for guidance.
Attendees can sign up using the Dev Days event calendar, which will show them the full calendar. Registration details are managed through Luma.
No, Dev Days events must be free to attend. You may set a capacity limit to adhere to your venue's capacity limits.
Core Content Session (Slide Deck): Dev Days content repository
You may choose to focus on the GitHub Copilot app or GitHub Copilot CLI for your event. The provided slide decks give a comprehensive, all-in-one resource covering the GitHub Copilot app or CLI.
Workshops
In addition to the core talk, we recommend including one workshop:
- Choose the workshop option that aligns with your selected topic and audience.
- Workshops are designed to be hands-on and practical, reinforcing the concepts covered in the talk.
- You do not need to run multiple workshops in a single event, but you can if you want.
Your event will be featured on the official Dev Days page, including your registration link. The page is promoted across Microsoft and GitHub social media channels.
What Code of Conduct do I and my attendees need to follow during my Dev Days event and within the event repository?
We have two Codes of Conduct related to the Dev Days series. Both can be found in the Dev Days repository.
- The Contributor Covenant Code of Conduct addresses our standards and expectations for conduct within this repository.
- The GitHub Event Code of Conduct addresses our standards and expectations for conduct at Dev Days events.
Ensure all attendees and organizers are aware of and agree to the Code of Conduct.
All Dev Days events must be marked Public on Luma so attendees can discover and register for your event.
All registrations must be managed through your Luma event page. Do not use external registration platforms or forms.
My community group uses a different registration platform (Meetup, Eventbrite, etc.). Can I use this platform for registration instead of Luma?
Your primary registration page should be the one that we provide you on Luma. You may utilize other platforms to further promote the event, but attendees should register on the Luma page.
Yes. Required registration questions must remain enabled on your Luma registration page.
Required registration questions include:
- Required for attendee: What country are you based in?
- Required for attendee: What is your GitHub username?
- Required for attendee: What is your job title?
- Not required for attendee: What company do you work for?
- Not required for attendee: Yes please, I'd like GitHub and Microsoft to use my information for personalized communications, targeted advertising and campaign effectiveness. See the GitHub Privacy Statement for more details.
Yes. If any event details change, especially the event date, update your Luma page and ensure all information remains accurate.
The program team will reach out to determine if receiving a Copilot Max coupon makes sense for your event and coordinate any complexities, if there are any.
- If you are a Microsoft/GitHub FTE, MVP, or GitHub Star, you should already be set up on the appropriate Copilot plans.
- If you are not associated with any of those groups, we'll review your account to ensure there are no reasons we won't be able to provide a coupon, mainly if you already have another coupon on your account.
- If you know you already have a student or other coupon associated with your account, we'd recommend utilizing a different account to be able to run the workshop effectively.
Swag eligibility is based on the benefits approved for your event. Refer to your event approval communication for details.
Please reach out to our swag partner at github@succinctive.com or ping the team in the Slack channel.
F&B support is available and may be requested in the onboarding form.
- You must pay for F&B upfront and submit a receipt for reimbursement. The reimbursement is processed through Plain Sight, a Microsoft vendor. This is the standard process for all organizers.
- Include your estimated number of attendees and total F&B cost in your event request.
- Support is limited to USD $400 per event, on a first-come, first-served basis.
- We will not reimburse expenses without prior approval. Please ensure your event and F&B request has been approved in advance.
You can expect to receive your payment request within 30 days. On average, payments are typically received within 10 - 15 business days after the invoice has been submitted, as long as all of the payment information has been received by Plain Sight.
Feel free to request payment in USD or whatever currency you used to pay for food and beverages. Plain Sight will pay you in your preferred currency, but please be sure to indicate on your invoice which form of currency you're requesting for payment.
Yes. Plain Sight will issue payment to the business or individual listed on your invoice, even if that person is not the point of contact for the event. Just make sure that the payment details are accurately listed on the invoice.
For those requesting to be paid via wire transfer, check, or ACH, Plain Sight will reach out via email to notify you once they have reviewed your reimbursement request. They will then send you a link to complete your one-time profile for payment processing. The email link will come from Rho Banking, and the account name will be Get to Work, Inc. d/b/a Plain Sight.
When you receive the email from Rho, click the link and insert your payment details. Having you insert the information directly provides Plain Sight with the most accurate verification against your invoice. Once complete, Plain Sight will get the payment sent out.
For questions or status updates about your reimbursement request, contact deleon@plainsighthq.com via email.
Please be sure to include receipts in your post-event report that have been provided to you by the vendor(s) after you purchased the food and beverages for the event. These receipts should not be quotes. Receipts should show how much was paid as well as what items were included with your purchase.
Attendees can complete the post-event survey here: Dev Days Attendee Survey.
Yes. All Dev Days organizers must complete the post-event organizer survey, regardless of whether they request Food & Beverage reimbursement: Dev Days Organizer Survey.
Completing the survey is required and helps us improve future Dev Days events.