: A desktop 2-player tank shooter game built on Java using the libGDX library. It's a mock-up of the classic tank battle games, where two players can compete head-to-head in armored combat.
Why is this trend growing? It taps into a specific developer psychology. When you’re waiting 15 minutes for a pipeline to finish, you aren't going to open a separate gaming app (which might look bad to your manager). But opening a gitlab.io URL? That looks like documentation. gitlab 2 player games
Many teams use GitLab to collaborate on small co-op games for jams. These focus on two players helping each other overcome obstacles. : A desktop 2-player tank shooter game built
Clone the repository locally, replace a white square with your emoji ( ❌ or ⭕ ), commit with a message like git commit -m "Player 1: Center square" , and push. The Future of Git-Based Gaming It taps into a specific developer psychology
This isn't standard chess. When you capture a piece, you must correctly answer a YAML syntax question (e.g., "Correct this broken .gitlab-ci.yml block" ). If you get it wrong, the capture is reversed. Audience: Hardcore DevOps engineers. If you aren't familiar with indentation, you will lose immediately.