feat: add file with git history

### Class 2 homework

**Deadline**: XX. February 2025, 23:59

**Deadline**: 11. March 2025, 23:59

* Create a new file in `class2_homework/` subdirectory of this repository with

  a name `<UCO>.txt`. Content of the file is up to you: it can be your

  favourite hobby, a cooking recipe, a book, ...

  a name `<UCO>.txt`. Write in this file what you'd like to see covered in the

  course or a suggest a topic for the last class.

* Commit the change.

* Push the change to your fork, **not** to the main branch (Hint: imagine a

  merge request would be a next step).

  `git` binary invocations. Put the history in a new file `<UCO>_commands.txt`

  and place it in the same directory and the same branch, commit it and push

  it. We want to see how you use git so we're sure we're teaching effectively.

  This is how to directory should look:

  This is how the directory should look after you're done:

```bash

$ tree class2_homework/

 class2_homework

 1 directory, 2 files

$ cat class2_homework/*

$ cat class2_homework/255490_commands.txt

git foo

git bar

cat dog

My favourite book series now is from Jeffery Deaver: Lincoln Rhyme.

baz

```

### Class 3 homework

**Deadline**: XX. XXX 2025, 23:59

**Deadline**: 18. March 2025, 23:59

The outcome of class 3 homework will be a merge request in this repository.

It's similar as class 2 homework, except we want a merge request this time and

it needs to be merged.

- Create a new file in `class3_homework/` subdirectory of this repository with

  a name `<UCO>.txt`. Tell us what you enjoy so far on the course, what new you

  have learned and used already. We'd also appreciate if something is missing.

- Make sure the merge request complies with all the best practices from the class.

- You have to create the merge request in this upstream repository. Merge

  requests in forks (origin remote) will be ignored.

- Tomas and Irina will review all upstream merge requests: you may be asked to

  a name `<UCO>.txt`. Tell us what you've learnt so far that was previously

  unclear to you.

- Make sure the merge request *complies with all the best practices* from the

  class.

- You have to create the merge request in this upstream repository.

  **Merge requests in forks (origin remote) will be ignored.**

- Michal and Tomas will review all upstream merge requests: you may be asked to

  correct something.

- Your merge request needs to be merged to pass this class.

- Your merge request needs to be merged to pass this homework.

- After you've done all of the above, save your command history, especially all

  `git` binary invocations. Put the history in a new file `<UCO>_commands.txt`

  and place it in the same directory and the same branch, commit it and push

  it. We want to see how you use git so we're sure we're teaching effectively.

  If you are asked to change something, no need to account for these commands.

  it. We want to see how you use git so we're sure we're teaching well.

- If you are asked to change something, you don't need to update the commands

  file.

### Class 4 homework

My favourite book series now is from Jeffery Deaver: Lincoln Rhyme.

I'd like to see worktrees covered in class 6.

git foo

git bar

cat dog

baz

Hello World :D