> 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/foundation/git/week1/assignment.md).

# Assignment

Finish all exercises from the session, then do the following:

## Exercise 1

In this exercise you will get some practice submitting your assignment by pushing it to GitHub and then creating a pull request (PR). You will be using this workflow every week to submit your assignment, so it's important that you get comfortable with it. You will also practice adding/committing files one by one.

1. Create a new repository in your GitHub called `hyf-foundation` (this will be your Assignments Repository). Clone it locally.
2. In your terminal, navigate to the freshly cloned repository on your computer
3. Go to branch `main`
4. Pull the latest changes to make sure your local `main` is up to date
5. Create a branch for your assignment, named `git-week1`, and move to that branch
6. Create a folder called `git` and inside of it another folder called `week1`.
7. Inside the `week1` folder create 3 new files:
   * a file named `my-favourite-food.txt`, inside the file write your favourite dish recipe (you can just find a random recipe on Google and paste it in the file ;)
   * a file named `my-second-favourite-food.txt`, inside the file write the recipe for your second favourite dish
   * a file named `countries.txt`, where you list three countries that you have visited (this doesn't need to be true, you can just write the names of three random countries)
8. Add and commit the file `my-favourite-food.txt`
9. Add and commit the file `my-second-favourite-food.txt`
10. Add and commit the file `countries.txt`
11. Push your changes into your assignment repository on GitHub
12. Go to GitHub and create a pull request (PR) from the branch `git-week1` to `main`
13. Add a link to your PR on the Assignment Sheet under the `GIT 1` column

## Cheat sheet / tips

Commands that you will need:

* `git branch <branch-name>` - to create a new branch named `<branch-name>`
* `git checkout <branch-name>` - to move to a branch named `<branch-name>`
* `git add <file_name>` - tell git to start tracking a file and to update what will be committed
* `git add .` - add all modified files to staging for commit
* `git commit -m "commit_message"` - commit (save) your changes
* `git push origin <branch-name>` - push (upload) your changes in your current branch to your GitHub repository into the branch named `<branch-name>`.

***Note*** For the sake of consistency (and to avoid mistakes), make sure that when you push you do it to a branch with the same name as the branch where you are, e.g. if you are on a branch named `git-week1` then push to a branch named `git-week1` by typing `git push origin git-week1`.

When pulling, if you want to pull from a branch named, for instance `main`, make sure that you are in a branch with the same name (`main`) on your computer as well, and only then do `git pull origin <branch-name>`.

Other useful git commands:

* `git status` - remember, it is your best friend, it tells you what is the state of your repository and sometimes what you should do.
* `git branch` - this is your second best friend, it tells you in which branch you are (you can also see where you are when you do `git status`)
* `git log`
* `git log --oneline`
* `git pull origin <branch-name>` - pull (download) your changes from your GitHub repository in the branch named `<branch-name>`, into your current local branch.

Command line commands that might be useful:

* `pwd`- print working directory, to know where you are
* `cd <folder_name>` - to go inside a folder named `<folder_name>`
* `cd ..`- to go to the parent folder of your current folder
* `mkdir <folder_name>` - to create a new folder
* `ls`- list all the folder contents
* `ls .*` - list all the folder contents, also invisible folders/files (e.g. the git folder)


---

# 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/foundation/git/week1/assignment.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.