> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/archive/jupyterhub/github-classroom-instructor-guide/overview.md). # Overview [GitHub Classroom](https://classroom.github.com) makes it easy to distribute materials and assigments to students while maintaining the ownership in your own organization. The following diagrams will help you understand these workflows. To get started follow guides in the remider of this section. ## Why use GitHub Classroom: * **Introduce students to version control**, one of the most important and foundational practices in software engineering. * **Automate assigment set up:** Share a single link with your students. When they accept, they will have their own copy of the assignment inside your organization * **Configure assignments:** Assigments can be configured to be individual or for groups, private or public . * **Download all repositories easily:** With GitHub's desktop client, Classroom Assistant. * **Keep you class materia organized year after year:** Version control is a good way to keep track of the material and changes that you make from one year to another. ## Possible Disadvantages: * Students and you will need to create an account in github * Students and you will need to learn a little bit if ***Version Countrol (git),*** * You may need to spend a class on the basics of ***Git*** ## --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ccv.brown.edu/archive/jupyterhub/github-classroom-instructor-guide/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.