An interactive Git learning game!
Go to file
2020-11-25 14:47:04 +01:00
.github/workflows CI: Deploy to itch.io 2020-11-02 18:55:54 +01:00
cards Bisect level :D 2020-10-30 12:08:17 +01:00
fonts Make fonts 15% larger 2020-11-10 23:23:10 +01:00
images Add file modification icons 2020-11-03 15:03:14 +01:00
levels Handle files without a position in them. Streamline cards a bit. 2020-11-18 22:31:23 +01:00
nodes File explorer document icon 2020-10-27 18:21:57 +01:00
resources Handle files without a position in them. Streamline cards a bit. 2020-11-18 22:31:23 +01:00
scenes Create inventory directory when loading a level 2020-11-25 14:47:04 +01:00
scripts Only drag one file with drag and drop, pretty ordering when taking/dropping 2020-11-25 14:39:52 +01:00
sounds Card particles and more sound effects 2020-10-22 16:19:22 +02:00
styles Start building a more graphical file browser 2020-10-23 13:07:16 +02:00
.gitignore Add Windows build to the CI 2020-10-20 11:11:29 +02:00
CODE_OF_CONDUCT.md Add Contributor Covenant v2.0 2020-10-12 20:00:59 +02:00
export_presets.cfg Export resources/ directory on all platforms 2020-10-30 19:20:53 +01:00
LICENSE.md Add Blue Oak Model License 1.0.0 2020-10-14 17:11:00 +02:00
Makefile Explain how to open the project in the Godot editor and how to build binaries 2020-11-10 23:40:42 +01:00
project.godot Restrict movement to arrow keys, switch to terminal by typing letters 2020-11-18 20:12:15 +01:00
README.md Explain how to open the project in the Godot editor and how to build binaries 2020-11-10 23:40:42 +01:00

git-hydra

git-hydra (working title) is an open-source game about learning Git!

The current form is an early prototype, and will change significantly until the end of February 2021.

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. Put your level in the contrib chapter.
  7. The dropdowns in the game will automatically refresh to contain your level, you don't need to restart the game.
  8. 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.

[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.

# 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 experiments/pull-merge-push level for an example.

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?

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

Logo of the German Ministry for Education and Research            Logo of the Prototype Fund            Logo of the Open Knowledge Foundation Germany

Thanks

License

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