├── .gitignore ├── .markdownlint.json ├── .github └── dependabot.yml ├── SUPPORT.md ├── LICENSE ├── .devcontainer └── devcontainer.json ├── SECURITY.md ├── CODE_OF_CONDUCT.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | # Replace the .gitignore with the appropriate one from https://github.com/github/gitignore -------------------------------------------------------------------------------- /.markdownlint.json: -------------------------------------------------------------------------------- 1 | { 2 | "default": true, 3 | "MD003": { "style": "atx" }, 4 | "MD007": { "indent": 4 }, 5 | "MD033": { "allowed_elements": ["kbd"] }, 6 | "no-hard-tabs": false, 7 | "whitespace": false, 8 | "MD013": { 9 | "line_length": 80, 10 | "code_blocks": false, 11 | "tables": false 12 | } 13 | } -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | # This is the dependabot configuration file that automates dependency updates 2 | # Updates section configures how dependabot should handle dependency updates: 3 | # - Monitors GitHub Actions workflow dependencies in the root directory 4 | # - Checks for updates weekly 5 | # 6 | # Learn more at https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#configuration-options-for-the-dependabotyml-file -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # Support 2 | 3 | ## How to file issues and get help 4 | 5 | This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue. 6 | 7 | For help or questions about using this project, please raise a GitHub issue. Copilot in a box is under active development and maintained by GitHub staff and the community. We will do our best to respond to support, feature requests, and community questions in a timely manner. 8 | 9 | ## GitHub Support Policy 10 | 11 | Support for this project is limited to the resources listed above. -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright GitHub, Inc. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. -------------------------------------------------------------------------------- /.devcontainer/devcontainer.json: -------------------------------------------------------------------------------- 1 | // For format details, see https://aka.ms/devcontainer.json. For config options, see the 2 | // README at: https://github.com/devcontainers/templates/tree/main/src/go 3 | { 4 | "name": "Game of Life Walkthrough", 5 | // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile 6 | "image": "mcr.microsoft.com/devcontainers/universal:latest", 7 | 8 | // Use 'forwardPorts' to make a list of ports inside the container available locally. 9 | "forwardPorts": [ 10 | 3000 11 | ], 12 | 13 | // Use 'postCreateCommand' to run commands after the container is created. 14 | // "postCreateCommand": "" 15 | 16 | // Configure tool-specific properties. 17 | "customizations": { 18 | "codespaces": { 19 | "openFiles": [ 20 | "README.md" 21 | ] 22 | }, 23 | "vscode": { 24 | "extensions": [ 25 | "GitHub.codespaces", 26 | "GitHub.copilot", 27 | "GitHub.copilot-chat", 28 | "github.copilot-workspace", 29 | "GitHub.remotehub", 30 | "github.vscode-github-actions", 31 | "GitHub.vscode-pull-request-github", 32 | "ms-vscode.live-server" 33 | ] 34 | } 35 | } 36 | 37 | // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. 38 | // "remoteUser": "root" 39 | } 40 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | Thanks for helping make GitHub safe for everyone. 2 | 3 | # Security 4 | 5 | GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub). 6 | 7 | Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. 8 | 9 | ## Reporting Security Issues 10 | 11 | If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure. 12 | 13 | **Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.** 14 | 15 | Instead, please send an email to opensource-security[@]github.com. 16 | 17 | Please include as much of the information listed below as you can to help us better understand and resolve the issue: 18 | 19 | * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) 20 | * Full paths of source file(s) related to the manifestation of the issue 21 | * The location of the affected source code (tag/branch/commit or direct URL) 22 | * Any special configuration required to reproduce the issue 23 | * Step-by-step instructions to reproduce the issue 24 | * Proof-of-concept or exploit code (if possible) 25 | * Impact of the issue, including how an attacker might exploit the issue 26 | 27 | This information will help us triage your report more quickly. 28 | 29 | ## Policy 30 | 31 | See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms) -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at . All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 71 | version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # GitHub Copilot in a Box 2 | 3 | This repository contains links to several sample projects, walkthroughs and videos that help you get started with GitHub Copilot. 4 | 5 | To get started with the Copilot in a Box materials, click on the [Releases](https://github.com/github-samples/copilot-in-a-box/releases) section of this repository. It should appear on the right hand side in full screen mode, or at the bottom of the page when viewing in a collapsed window or device with a smaller screen. 6 | 7 | ## Useful Resources 8 | 9 | The following resources are useful for learning more about GitHub Copilot. Have something to add? Please submit a pull request! 10 | 11 | ### Samples 12 | 13 | - [skills/getting-started-with-github-copilot](https://github.com/skills/getting-started-with-github-copilot) (< 1hr) 14 | - An exercise which introduces GitHub Copilot from the groundup. It includes a series of steps that help you learn about Code Completions, Chat and more. 15 | - [skills/integrate-mcp-with-copilot](https://github.com/skills/integrate-mcp-with-copilot) (< 1hr) 16 | - An exercise which introduces GitHub Copilot Agent Mode and the concept of Model Context Protocol (MCP) servers. 17 | - [github-samples/game-of-life-walkthrough](https://github.com/github-samples/game-of-life-walkthrough) (< 1hr) 18 | - A self-guided walkthrough that introduces GitHub Copilot (including Chat, Edits, Copilot instructions), leading up to a GitHub-themed Game of Life implementation on GitHub Pages. 19 | - [github-samples/copilot-hack](https://github.com/github-samples/copilot-hack) 20 | - A set of challenges focused on GitHub Copilot. The challenges are more open-ended than the exercises in the other repositories, and are designed to encourage attendees to think through how they would use GitHub Copilot in their own projects. 21 | - [microsoft/CopilotHackathon](https://github.com/microsoft/CopilotHackathon) 22 | - A library of GitHub Copilot challenges, including a variety of samples (NodeJS, .NET, Java, Data Scientists, Python Engineers). 23 | - [github-samples/pets-workshop](https://github.com/github-samples/pets-workshop) 24 | - Two versions of a workshop that can be used either: 25 | - 1h version that introduces the core capabilities of GitHub Copilot 26 | - Full day version that introduces the wider GitHub platform including Codespaces, GitHub Advanced Security, GitHub Actions, as well as the core capabilities of GitHub Copilot. 27 | - [github-samples/agents-in-sdlc](https://github.com/github-samples/agents-in-sdlc) 28 | - A workshop (generally takes 1.5h - 2h dependent on previous experience), focusing on Copilot coding agent, Copilot agent mode, Copilot Instructions and more. 29 | 30 | ### Guides 31 | 32 | - [How to write better prompts for GitHub Copilot](https://github.blog/developer-skills/github/how-to-write-better-prompts-for-github-copilot/) 33 | - [Copilot Chat Cookbook](https://github.blog/developer-skills/github/how-to-write-better-prompts-for-github-copilot/) 34 | - [How to refactor code with GitHub Copilot](https://github.blog/ai-and-ml/github-copilot/how-to-refactor-code-with-github-copilot/) 35 | - [How to debug code with GitHub Copilot](https://github.blog/ai-and-ml/github-copilot/how-to-debug-code-with-github-copilot/) 36 | 37 | ### Videos 38 | 39 | - [Live demo: GitHub Copilot in Visual Studio Code](https://www.youtube.com/watch?v=dSbv-1KGu2U) 40 | - [How GitHub Next took Copilot Workspace from Concept to Code](https://www.youtube.com/watch?v=f3Yrms9r_n4) 41 | - [Building apps with GitHub Copilot: A developer's perspective](https://www.youtube.com/watch?v=bsSAywnqptc) 42 | - [AI-powered development: Exploring the latest GitHub Copilot features](https://www.youtube.com/watch?v=07mUcfiTpag) 43 | - [Build Conway's Game of Life with GitHub Copilot Free](https://www.youtube.com/watch?v=pGV_T6g1hcU) 44 | - [How to get started with GitHub Copilot Free in Visual Studio Code](https://www.youtube.com/watch?v=dMbOh114Vd4) 45 | - [Testing with GitHub Copilot](https://www.youtube.com/watch?v=smdBqEu7fx4) 46 | - [GitHub Copilot Chat and o1-preview: Building a maze generator!](https://www.youtube.com/watch?v=HxoCaobgg70) 47 | - [GitHub Copilot: the agent awakens](https://www.youtube.com/watch?v=C95drFKy4ss) 48 | - [New GitHub Copilot code completion model: GPT-4o Copilot](https://www.youtube.com/watch?v=Oi_O6SZZWPc) 49 | - [Demo: Using Claude 3.7 Sonnet with GitHub Copilot](https://www.youtube.com/watch?v=LHVLyqc_WBM) 50 | 51 | ## Contributing 52 | 53 | This repository is maintained by GitHub's Developer Relations team. If you have a sample project, walkthrough, or video that you would like to add, please submit a pull request. If you have any questions or suggestions (particularly about the slides), please raise an issue. 54 | 55 | ## License 56 | 57 | The code in this repository is licensed under the MIT License. See the [LICENSE](LICENSE) file for more information. The content (including the PowerPoint deck and any other materials published as a release) are [released under CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/). 58 | 59 | The MIT license grant is not for GitHub's trademarks, which include the logo designs. GitHub reserves all trademark and copyright rights in and to all GitHub trademarks. GitHub® and its stylized versions and the Invertocat mark are GitHub's Trademarks or registered Trademarks. When using GitHub's logos, be sure to follow the GitHub logo guidelines. 60 | --------------------------------------------------------------------------------