ld51/particle-clash
ld51/particle-clash
1
Fork 0
mirror of https://github.com/Steffo99/particle-clash.git synced 2024-11-21 15:14:19 +00:00
Code Activity
Match-4 game for two players about particles about to collide
19 commits 1 branch 6 tags 5.9 MiB
GDScript 100%
Find a file
Stefano Pigozzi 0385ad5dc1
Post-build updates
2022-10-02 17:28:22 +02:00
.github/workflows I pressed Ctrl+Z too many times 2022-10-02 16:03:52 +02:00
.vscode Complete (more or less) the game 2022-10-02 14:36:34 +02:00
media Post-build updates 2022-10-02 17:28:22 +02:00
src Post-build updates 2022-10-02 17:28:22 +02:00
.gitattributes Initial commit 2022-09-30 23:47:28 +02:00
.gitignore Post-build updates 2022-10-02 17:28:22 +02:00
default_bus_layout.tres Complete (more or less) the game 2022-10-02 14:36:34 +02:00
export_presets.cfg Post-build updates 2022-10-02 17:28:22 +02:00
project.godot Update exports 2022-10-02 15:39:36 +02:00
README.md Update README 2022-10-02 15:49:33 +02:00

README.md

Particle Clash

A match-4 game for two players about particles about to collide

Ludum Dare 51: Compo entry

Overall: TBD Fun: TBD Innovation: TBD Theme: TBD Graphics: TBD Audio: TBD Humor: TBD Mood: TBD

About

TODO

Credits

Game

  • Stefano Pigozzi (@Steffo99)

Tools

Development

Large file storage

This repository is configured with the Git Large File Storage extension.

Cloning

To clone this repository with all LFS files:

  1. Ensure Git LFS is installed on your system

  2. Clone the repository normally

  3. Run:

    $ git lfs pull

Committing

Before you commit a large binary file (such as an image, or an audio file):

  1. Ensure the Git LFS hooks are installed:

    $ git lfs install

  2. Ensure the extension of the file you are committing is tracked:

    $ git lfs track "*.ext"

  3. Ensure the .gitattributes file itself is tracked:

    $ git add .gitattributes

Auto-build

To trigger an automatic export of the project:

  1. Ensure GitHub Actions are enabled
  2. Push a new tag with formatted as vX.Y.Z

To download the resulting builds:

  1. Visit the Actions tab
  2. Click on the triggered workflow
  3. Download the created artifacts from the bottom of the page

Note that artifacts are visible only if you're logged in to a GitHub account!