> For the complete documentation index, see [llms.txt](https://program.hackyourfuture.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://program.hackyourfuture.dk/course-content/shared-modules/collaboration-via-github.md).

# Collaboration via GitHub

The main goal of this module is to become comfortable with branches, merge conflicts, and pull requests, so that you can and feel comfortable working together with other developers using GitHub.

| Week | Topic                                                                            | Preparation                                                                                 | Session Plan                                                                                  | Assignment                                                                                |
| ---- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| 1.   | [Advanced Git](/course-content/shared-modules/collaboration-via-github/week1.md) | [Preparation](/course-content/shared-modules/collaboration-via-github/week1/preparation.md) | [Session Plan](/course-content/shared-modules/collaboration-via-github/week1/session-plan.md) | [Assignment](/course-content/shared-modules/collaboration-via-github/week1/assignment.md) |

## Module Learning Goals

By the end of this module, you will be able to:

* [ ] How to write a good commit message and submit easy to understand PRs
* [ ] Understand why we use branches and the different types
* [ ] Practice using branches and handling changes between local and remote
* [ ] Understand what a merge conflict is and how to resolve them
* [ ] How to save temporary changes without committing them (ie. git stash)
* [ ] How to "remove" commits using reset (soft vs hard), revert, cherry-pick and rebase
* [ ] Be prepared to collaborate successfully using GitHub on your final project
* [ ] How to use git tags and semantic versioning
* [ ] Know the main git workflows (feature-branch, gitflow, forking) and when to use each


---

# 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://program.hackyourfuture.dk/course-content/shared-modules/collaboration-via-github.md?ask=<question>&goal=<user_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.