Oh My Git! is an open-source game about learning Git!

Play the game!

You can download binaries for Linux, macOS, and Windows from itch.io!

Report bugs!

If something doesn't work or looks broken, please let us know! You can describe the issue you're having in our issue tracker.

If you have ideas for new features, we'd be excited to hear them! Also in that case, we invite you to open an issue!

Build your own level!

Wanna build your own level? Great! Here's how to do it:

1. Download the latest version of the Godot game engine.
2. Clone this repository.
3. Run the game – the easiest way to do so is to run godot scenes/main.tscn from the project directory.
4. Get a bit familiar with the levels which are currently there.
5. Take a look into the levels directory. It's split into chapters, and each level is a file.
6. Make a copy of an existing level or start writing your own. See the documention of the format below.
7. Write and test your level. If you're happy with it, feel free to send it to us in a pull request! <3

Level format

title = This is the level's title

[description]

This text will be shown when the level starts.

It describes the task or puzzle the player can solve.

[cli]

(optional) This text will be shown below the level description in a darker color.

It should give hints to the player about command line usage and also maybe some neat tricks.

[congrats]

This text will be shown after the player has solved the level.

Can contain additional information, or bonus exercises.

[setup]

# Bash commands that set up the initial state of the level. An initial
# `git init` is always done automatically. The default branch is called `main`.

echo You > people_who_are_awesome
git add .
git commit -m "Initial commit"

[win]

# Bash commands that check whether the level is solved. Write these as if you're
# writing the body of a Bash function. Make the function return 0 if it's
# solved, and a non-zero value otherwise. You can use `return`, and also, Bash
# functions return the exit code of the last statement, which sometimes allows
# very succinct checks. The comment above the win check will be shown in the game
# as win condition text.

# Check whether the file has at least two lines in the latest commit:
test "$(git show HEAD:people_who_are_awesome | wc -l)" -ge 2

A level can consist of multiple repositories. To have more than one, you can use sections like [setup <name>] and [win <name>], where <name> is the name of the remote. The default name is "yours". All repositories will add each other as remotes. Refer to the remote levels examples.

Level guidelines

At this stage, we're still exploring ourselves which kind of levels would be fun! So feel free to try new things: basic introductions with a little story? Really hard puzzles? Levels where you have to find information? Levels where you need to fix a problem? Levels with three remotes?

Add localizations

1. Add the localization text into the section "description" in the file ./resource/cards.json

Example:
"description": {
   "en_EN": "Drag this card into the empty space above to initialize the time machine!",
   "it_IT": "Trascina questa carta nell'area vuota sopra per inizializzare la macchina del tempo",
   "es_ES": "Arrastre esta tarjeta al área en blanco de arriba para inicializar la máquina del tiempo"
}

2. Add, into the directory levels, the directory with the levels do you want to adding (es. ./levels/fr_FR/LIVELLI )
3. Add, the localization into the dictionary game.langs (es. var langs = {0: "en_EN", 1: "it_IT", 2: "es_ES"} the first and default localization it must be en_EN
4. Add column of specific locale and relative traductions for avery keys in the file ./resource/localization.csv

Example:

keys,en,it,es
LEVELS,Livels,Livelli,niveles
QUIT,Quit,Esci,Salir
BACK,Back,Indietro,Espalda

If one or more localizations in the descriptions of cards are missing and levels require that card, the game crashes!

Contribute code!

To open the game in the Godot editor, run godot project.godot. You can then run the game using F5.

Feel free to make improvements to the code and send pull requests! There is one exception: because merge conflicts in Godot's scene files tends to be hard to resolve, before working on an existing *.tscn file, please get in touch with us.

To build your own binaries, you'll need Godot's export templates, and zip, wget, and 7z. Then, run make. On Debian/Ubuntu, the Godot binary is called godot3, you might need to adjust the paths in the Makefile.

Code of Conduct

We have a Code of Conduct in place that applies to all project contributions, including issues and pull requests.

Funded by

                       

Thanks

• "success" sound by Leszek_Szarzy, CC0
• "swish" sound by jawbutch, CC0
• "swoosh" sound by WizardOZ, CC0
• "poof" sound by Saviraz, CC0
• "buzzer" sound by Loyalty_Freak_Music, CC0
• "typewriter_ding" sound by _stubb, CC0

License

Blue Oak Model License 1.0.0 – a modern alternative to the MIT license. It's a a pleasant read! :)